 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| CYRF69103 Programmable Radio on Chip Low Power PRoCTM LP Features Single Device, Two Functions 8-bit, Flash based MCU function and 2.4 GHz radio transceiver function in a single device. Flash-Based Microcontroller Function M8C based 8-bit CPU, optimized for Human Interface Devices (HID) applications 256 Bytes of SRAM 8 Kbytes of Flash memory with EEPROM emulation In-System reprogrammable CPU speed up to 12 MHz 16-bit free-running timer Low power wakeup timer 12-bit Programmable Interval Timer with interrupts Watchdog timer Industry-Leading 2.4 GHz Radio Transceiver Function Operates in the unlicensed worldwide Industrial, Scientific, and Medical (ISM) band (2.4 GHz-2.483 GHz) DSSS data rates of up to 250 Kbps GFSK data rate of 1 Mbps -97 dBm receive sensitivity Programmable output power up to +4 dBm Auto Transaction Sequencer (ATS) Framing CRC and Auto ACK Received Signal Strength Indication (RSSI) Automatic Gain Control (AGC) Component Reduction Integrated 1.8V boost converter GPIOs that require no external components Operates off a single crystal Flexible IO 2 mA source current on all GPIO pins. Configurable 8-mA or 50-mA/pin current sink on designated pins Each GPIO pin supports high-impedance inputs, configurable pull up, open drain output, CMOS/TTL inputs, and CMOS output Maskable interrupts on all IO pins Operating voltage from 1.8V to 3.6V DC Operating temperature from 0 to 70C Pb-free 40-lead QFN package Advanced development tools based on Cypress's PSoC(R) tools Block Diagram 47F MOSI SCK nSS VCC 470nF VCC 10F VBat1 RST VBat0 VBat2 L/D VCC1 VCC2 VCC3 Vdd 470nF VDD_MICRO VReg VIO RFp RFn RFbias Microcontroller Function P0_1,3,4,7 4 P1_0:2,6:7 5 P2_0:1 GND 2 P1.5/MOSI P1.4/SCK P1.3/nSS Radio Function IRQ/GPIO MISO/GPIO XOUT/GPIO PACTL/GPIO RESV GND ..... 12MHz ....... Cypress Semiconductor Corporation Document #: 001-07611 Rev *C * 198 Champion Court * San Jose, CA 95134-1709 GND Xtal * 408-943-2600 Revised April 25, 2008 [+] Feedback CYRF69103 Applications The CYRF69103 PRoC LP is targeted for the following applications: The radio meets the following world-wide regulatory requirements: Wireless HID devices Mice Remote Controls Presenter tools Barcode scanners POS terminal General purpose wireless applications: Industrial applications Home automation White goods Consumer electronics Toys Europe ETSI EN 301 489-1 V1.4.1 ETSI EN 300 328-1 V1.3.1 North America FCC CFR 47 Part 15 Japan ARIB STD-T66 Data Transmission Modes The radio supports four different data transmission modes: In GFSK mode, data is transmitted at 1 Mbps, without any DSSS In 8DR mode, 1 byte is encoded in each PN code symbol transmitted In DDR mode, 2 bits are encoded in each PN code symbol transmitted In SDR mode, a single bit is encoded in each PN code symbol transmitted Functional Description PRoC LP devices are integrated radio and microcontroller functions in the same package to provide a dual-role single-chip solution. Communication between the microcontroller and the radio is via the radio's SPI interface. Functional Overview The CYRF69103 is a complete Radio System-on-Chip device, providing a complete RF system solution with a single device and a few discrete components. The CYRF69103 is designed to implement low-cost wireless systems operating in the worldwide 2.4 GHz Industrial, Scientific, and Medical (ISM) frequency band (2.400 GHz-2.4835 GHz). Both 64-chip and 32-chip data PN codes are supported. The four data transmission modes apply to the data after the Start of Packet (SOP). In particular, the packet length, data and CRC are all sent in the same mode. Microcontroller Function The MCU function is an 8-bit Flash-programmable microcontroller. The instruction set has been optimized specifically for HID and a variety of other embedded applications. The MCU function has up to eight Kbytes of Flash for user's code and up to 256 bytes of RAM for stack space and user variables. In addition, the MCU function includes a Watchdog timer, a vectored interrupt controller, a 16-bit Free-Running Timer, and 12-bit Programmable Interrupt Timer. The microcontroller has 15 GPIO pins grouped into multiple ports. With the exception of the four radio function GPIOs, each GPIO port supports high-impedance inputs, configurable pull up, open drain output, CMOS/TTL inputs and CMOS output. Up to two pins support programmable drive strength of up to 50 mA. Additionally, each IO pin can be used to generate a GPIO interrupt to the microcontroller. Each GPIO port has its own GPIO interrupt vector with the exception of GPIO Port 0. GPIO Port 0 has three dedicated pins that have independent interrupt vectors (P0.3 - P0.4). The microcontroller features an internal oscillator. The PRoC LP includes a Watchdog timer, a vectored interrupt controller, a 12-bit programmable interval timer with configurable 1-ms interrupt and a 16-bit free-running timer with capture registers. In addition, the CYRF69103 IC has a Power Management Unit (PMU), which allows direct connection of the device to any battery voltage in the range 1.8V to 3.6V. The PMU conditions the battery voltage to provide the supply voltages required by the device, and may supply external devices. 2.4 GHz Radio Function The SoC contains a 2.4 GHz 1-Mbps GFSK radio transceiver, packet data buffering, packet framer, DSSS baseband controller, Received Signal Strength Indication (RSSI), and SPI interface for data transfer and device configuration. The radio supports 98 discrete 1 MHz channels (regulations may limit the use of some of these channels in certain jurisdictions). In DSSS modes the baseband performs DSSS spreading/despreading, while in GFSK Mode (1 Mb/s - GFSK) the baseband performs Start of Frame (SOF), End of Frame (EOF) detection and CRC16 generation and checking. The baseband may also be configured to automatically transmit Acknowledge (ACK) handshake packets whenever a valid packet is received. When in receive mode, with packet framing enabled, the device is always ready to receive data transmitted at any of the supported bit rates, except SDR, enabling the implementation of mixed-rate systems in which different devices use different data rates. This also enables the implementation of dynamic data rate systems, which use high data rates at shorter distances and/or in a low-moderate interference environment, and change to lower data rates at longer distances and/or in high interference environments. Document #: 001-07611 Rev *C Page 2 of 65 [+] Feedback CYRF69103 Backward Compatibility The CYRF69103 IC is fully interoperable with the main modes of the first generation Cypress radios namely the CYWUSB6934 -LS and CYWWUSB6935-LR devices. The 62.5 kbps mode is supported by selecting 32 chip DDR mode. Similarly, the 15.675 kbps mode is supported by selecting 64 chip SDR mode In this way, a suitably configured CYRF69103 IC device may transmit data to or receive data from a first generation device, or both. Backwards compatibility requires disabling the SOP, length, and CRC16 fields. Shown below are the different configurations of the registers and firmware that enable a new generation radio to communicate with a first generation radio.There are two possible modes: SDR and DDR mode (8-DR and GFSK modes are not present in the first generation radio). The second generation radio must be initialized using the RadioInitAPI of the LP radio driver and then the following registers' bits need to be configured to the given Byte values. Essentially, the following deactivates the added features of the second generation radio and takes it down to the level of the first generation radio; the data format, data rates, and the PN codes used arerecognizable by the first generation radio DDR Mode Table 1. DDR Mode Register TX_CFG_ADR RX_CFG_ADR Value 0X16 0X4B Description 32 chip PN Code, DDR, PA = 6 AGC is enabled. LNA and attenuator are disabled. Fast turn around is disabled, the device uses high side receive injection and Hi-Lo is disabled. Overwrite to receive buffer is enabled and the RX buffer is configured to receive eight bytes maximum. AutoACK is disabled. Forcing end state is disabled. The device is configured to transition to Idle mode after a Receive or Transmit. ACK timeout is set to 128 s. All SOP and framing features are disabled. Disable LEN_EN=0 if EOP is needed. Disable Transmit CRC-16. The receiver rejects packets with a zero seed. The Rx CRC-16 Checker is disabled and the receiver accepts bad packets that do not match the seed in CRC_seed registers. Basically this helps in communication with the first generation radio that does not have CRC capabilities. Set ALL SLOW. When set, the synthesizer settle time for all channels is the same as the slow channels in the first generation radio. Sets the number of allowed corrupted bits to 3. Sets the number of consecutive symbols for non-correlation to detect end of packet. AAAA are the two preamble bytes. Any other byte can also be written into the preamble register file. Recommended counts of the preamble bytes to be sent should be >4. XACT_CFG_ADR 0X05 FRAMING_CFG_AD R TX_OVERRIDE_AD R RX_OVERRIDE_AD R 0X00 0X04 0X14 ANALOG_CTRL_AD R DATA32_THOLD_AD R EOP_CTRL_ADR PREAMBLE_ADR 0X01 0X03 0x01 0xAAAA05 Document #: 001-07611 Rev *C Page 3 of 65 [+] Feedback CYRF69103 SDR Mode Table 2. SDR Mode Register TX_CFG_ADR RX_CFG_ADR Value 0X3E 0X4B Description 64 chip PN code, SDR mode, PA = 6. AGC is enabled. LNA and attenuator are disabled. Fast turn around is disabled, the device uses high side receive injection and Hi-Lo is disabled. Overwrite to receive buffer is enabled and RX buffer is configured to receive eight bytes maximum. Enables RXOW to allow new packets to be loaded into the receive buffer. This also enables the VALID bit which is used by the first generation radio's error correction firmware. AutoACK is disabled. Forcing end state is disabled. The device is configured to transition to Idle mode after Receive or Transmit. ACK timeout is set to 128 s. All SOP and framing features are disabled. Disable LEN_EN=0 if EOP is needed. Disable Transmit CRC-16. The receiver rejects packets with a zero seed. The RX CRC-16 checker is disabled and the receiver accepts bad packets that do not match the seed in the CRC_seed registers. Basically this helps in communication with the first generation radio that does not have CRC capabilities. Set ALL SLOW. When set, the synthesizer settle time for all channels is the same as the slow channels in the first generation radio, for manual ACK consistency Sets the number of allowed corrupted bits to 7 which is close to the recommended 12% value. Sets the number of consecutive symbols for non-correlation to detect end of packet. AAAA are the two preamble bytes. Any other byte can also be written into the preamble register file. Recommended counts of the preamble bytes to be sent should be >8. XACT_CFG_ADR 0X05 FRAMING_CFG_AD R TX_OVERRIDE_AD R RX_OVERRIDE_AD R 0X00 0X04 0X14 ANALOG_CTRL_AD R DATA64_THOLD_AD R EOP_CTRL_ADR PREAMBLE_ADR 0X01 0X07 0xA1 0xAAAA09 Document #: 001-07611 Rev *C Page 4 of 65 [+] Feedback CYRF69103 Pinout Pin 1 2 3, 7, 16 4 5 6 8 9 10 11 12 13 14, 17, 18, 20 15 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 Name P0.4 XTAL VCC P0.3 P0.1 Vbat1 P2.1 Vbat2 RFbias RFp GND RFn NC P2.0 RESV P1.0 P1.1 VDD_micro P1.2 P1.3 / nSS P1.4 / SCK IRQ P1.5 / MOSI MISO XOUT PACTL P1.6 VIO RST P1.7 VDD1.8 L/D P0.7 Vbat0 VREG E-pad Corner Tabs GPIO Reserved. Must connect to GND GPIO GPIO MCU supply connected to pin 40, max CPU 12 MHz GPIO Slave Select SPI Clock Radio Function Interrupt output, configure High, Low or as Radio GPIO MOSI pin from microcontroller function to radio function 3-wire SPI mode configured as Radio GPIO. In 4-wire SPI mode sends data to MCU function Buffered CLK, PACTL_n or Radio GPIO Control for external PA or Radio GPIO GPIO 1.8V to 3.6V to main power supply rail for Radio IO Radio Reset. Connected to pin 40 with 0.47 F. Must have a RST=HIGH event the very first time power is applied to the radio otherwise the state of the radio control registers is unknown GPIO Regulated logic bypass. Connected to 0.47F to GND Inductor/Diode connection for Boost. When Internal PMU is not being used connect L/D to GND. GPIO Connected to1.8V to 3.6V main power supply, through 0.047-F bypass C Boost regulator output voltage feedback Must be connected to ground Do Not connect corner tabs Individually configured GPIO 12 MHz crystal 2.4V to 3.6V supply. Connected to pin 40 (0.047-F bypass) Individually configured GPIO Individually configured GPIO Connect to 1.8V to 3.6V power supply, through 47-ohm series/1-F shunt C GPIO. Port 2 Bit 1 Connected to1.8V to 3.6V main power supply, through 0.047-F bypass C RF pin voltage reference Differential RF to/from antenna GND Differential RF to/from antenna Function/Description Document #: 001-07611 Rev *C Page 5 of 65 [+] Feedback CYRF69103 Pinout Diagram Figure 1. Pinout PACTL / GPIO 31 VDD_1.8 36 VBAT0 VREG 40 P1.7 35 P0.7 38 P1.6 32 RST 34 L/D 37 Corner tabs VIO 33 39 P0.4 XTAL VCC P0.3 P0.1 VBAT1 VCC P2.1 VBAT2 1 2 3 4 5 6 7 8 9 * E-PAD Bottom Side 30 XOUT / GPIO 29 MISO / GPIO CYRF69103 WirelessUSB LP 28 P1.5 / MOSI 27 IRQ / GPIO 26 P1.4 / SCK 25 P1.3 / SS 24 P1.2 23 VDD_Micro 22 P1.1 21 P1.0 RFBIAS 10 11 RFP 12 GND 13 RFN 14 NC 15 P2.0 16 VCC 17 NC 18 NC 19 RESV 20 NC Functional Block Overview All the blocks that make up the PRoC LP are presented here. Baseband and Framer The baseband and framer blocks provide the DSSS encoding and decoding, SOP generation and reception and CRC16 generation and checking, and EOP detection and length field. Data Transmission Modes and Data Rates The SoC supports four different data transmission modes: 2.4 GHz Radio The radio transceiver is a dual conversion low IF architecture optimized for power and range/robustness. The radio employs channel-matched filters to achieve high performance in the presence of interference. An integrated Power Amplifier (PA) provides up to +4 dBm transmit power, with an output power control range of 34 dB in 7 steps. The supply current of the device is reduced as the RF output power is reduced. Table 3. Internal PA Output Power Step Table PA Setting 7 6 5 4 3 2 1 0 Typical Output Power (dBm) +4 0 -5 -10 -15 -20 -25 -30 In GFSK mode, data is transmitted at 1 Mbps, without any DSSS. In 8DR mode, 8 bits are encoded in each DATA_CODE_ADR derived code symbol transmitted. In DDR mode, 2-bits are encoded in each DATA_CODE_ADR derived code symbol transmitted. (As in the CYWUSB6934 DDR mode). In SDR mode, 1 bit is encoded in each DATA_CODE_ADR derived code symbol transmitted. (As in the CYWUSB6934 standard modes.) Both 64-chip and 32-chip DATA_CODE_ADR codes are supported. The four data transmission modes apply to the data after the SOP. In particular the length, data, and CRC16 are all sent in the same mode. In general, lower data rates reduces packet error rate in any given environment. The CYRF69103 IC supports the following data rates: 1000-kbps (GFSK) 250-kbps (32-chip 8DR) 125-kbps (64-chip 8DR) 62.5-kbps (32-chip DDR) 31.25-kbps (64-chip DDR) 15.625-kbps (64-chip SDR) Frequency Synthesizer Before transmission or reception may commence, it is necessary for the frequency synthesizer to settle. The settling time varies depending on channel; 25 fast channels are provided with a maximum settling time of 100 s. The "fast channels" (<100-s settling time) are every 3rd frequency, starting at 2400 MHz up to and including 2472 MHz (i.e., 0,3,6,9.......69 & 72). Document #: 001-07611 Rev *C Page 6 of 65 [+] Feedback CYRF69103 Lower data rates typically provide longer range and/or a more robust link. Link Layer Modes The CYRF69103 IC device supports the following data packet framing features: SOP - Packets begin with a 2-symbol Start of Packet (SOP) marker. This is required in GFSK and 8DR modes, but is optional in DDR mode and is not supported in SDR mode; if framing is disabled then an SOP event is inferred whenever two successive correlations are detected. The SOP_CODE_ADR code used for the SOP is different from that used for the "body" of the packet, and if desired may be a different length. SOP must be configured to be the same length on both sides of the link. EOP - There are two options for detecting the end of a packet. If SOP is enabled, then a packet length field may be enabled. GFSK and 8DR must enable the length field. This is the first 8 bits after the SOP symbol, and is transmitted at the payload data rate. If the length field is enabled, an End of Packet (EOP) condition is inferred after reception of the number of bytes defined in the length field, plus two bytes for the CRC16 (if enabled--see below). The alternative to using the length field is to infer an EOP condition from a configurable number of successive non-correlations; this option is not available in GFSK mode and is only recommended when using SDR mode. CRC16 - The device may be configured to append a 16-bit CRC16 to each packet. The CRC16 uses the USB CRC polynomial with the added programmability of the seed. If enabled, the receiver will verify the calculated CRC16 for the payload data against the received value in the CRC16 field. The starting value for the CRC16 calculation is configurable, and the CRC16 transmitted may be calculated using either the loaded seed value or a zero seed; the received data CRC16 will be checked against both the configured and zero CRC16 seeds. CRC16 detects the following errors: Any one bit in error Any two bits in error (no matter how far apart, which column, and so on) Any odd number of bits in error (no matter where they are) An error burst as wide as the checksum itself Figure 2 shows an example packet with SOP, CRC16 and lengths fields enabled. Figure 2. Example Default Packet Format P re a m b le n x 16us 2 n d F ra m in g S y m b o l* P SOP 1 1 s t F ra m in g S y m b o l* SOP 2 L e n g th Packet le n g th 1 B y te P e rio d P a y lo a d D a ta C R C 16 * N o te :3 2 o r 6 4 u s Packet Buffers and Radio Configuration Registers Packet data and configuration registers are accessed through the SPI interface. All configuration registers are directly addressed through the address field in the SPI packet (as in the CYWUSB6934). Configuration registers are provided to allow configuration of DSSS PN codes, data rate, operating mode, interrupt masks, interrupt status, and others. Packet Buffers All data transmission and reception uses the 16-byte packet buffers--one for transmission and one for reception. The transmit buffer allows a complete packet of up to 16 bytes of payload data to be loaded in one burst SPI transaction, and then transmitted with no further MCU intervention. Similarly, the receive buffer allows an entire packet of payload data up to 16 bytes to be received with no firmware intervention required until packet reception is complete. The CYRF69103 IC supports packet length of up to 40 bytes; interrupts are provided to allow an MCU to use the transmit and receive buffers as FIFOs. When transmitting a packet longer than 16 bytes, the MCU can load 16 bytes initially, and add further bytes to the transmit buffer as transmission of data creates space in the buffer. Similarly, when receiving packets longer than 16 bytes, the MCU must fetch received data from the FIFO periodically during packet reception to prevent it from overflowing. Auto Transaction Sequencer (ATS) The CYRF69103 IC provides automated support for transmission and reception of acknowledged data packets. When transmitting a data packet, the device automatically starts the crystal and synthesizer, enters transmit mode, transmits the packet in the transmit buffer, and then automatically switches to receive mode and waits for a handshake packet--and then automatically reverts to sleep mode or idle mode when either an ACK packet is received, or a time-out period expires. Similarly, when receiving in transaction mode, the device waits in receive mode for a valid packet to be received, then automatically transitions to transmit mode, transmits an ACK packet, and then switches back to receive mode to await the next packet. The contents of the packet buffers are not affected by the transmission or reception of ACK packets. In each case, the entire packet transaction takes place without any need for MCU firmware action; to transmit data the MCU simply needs to load the data packet to be transmitted, set the length, and set the TX GO bit. Similarly, when receiving packets in transaction mode, firmware simply needs to retrieve the fully received packet in response to an interrupt request indicating reception of a packet. Page 7 of 65 Document #: 001-07611 Rev *C [+] Feedback CYRF69103 Interrupts The radio function provides an interrupt (IRQ) output, which is configurable to indicate the occurrence of various different events. The IRQ pin may be programmed to be either active high or active low, and be either a CMOS or open drain output. The radio function features three sets of interrupts: transmit, receive, and system interrupts. These interrupts all share a single pin (IRQ), but can be independently enabled/disabled. In transmit mode, all receive interrupts are automatically disabled, and in receive mode all transmit interrupts are automatically disabled. However, the contents of the enable registers are preserved when switching between transmit and receive modes. If more than one radio interrupt is enabled at any time, it is necessary to read the relevant status register to determine which event caused the IRQ pin to assert. Even when a given interrupt source is disabled, the status of the condition that would otherwise cause an interrupt can be determined by reading the appropriate status register. It is therefore possible to use the devices without making use of the IRQ pin by polling the status register(s) to wait for an event, rather than using the IRQ pin. Power-On Reset/Low-Voltage Detect The power-on reset circuit detects logic when power is applied to the device, resets the logic to a known state, and begins executing instructions at Flash address 0x0000. When power falls below a programmable trip voltage, it generates reset or may be configured to generate interrupt. There is a low-voltage detect circuit that detects when VCC drops below a programmable trip voltage. It may be configurable to generate an LVD interrupt to inform the processor about the low-voltage event. POR and LVD share the same interrupt. There is not a separate interrupt for each. The Watchdog timer can be used to ensure the firmware never gets stalled in an infinite loop. Timers The free-running 16-bit timer provides two interrupt sources: the programmable interval timer with 1-s resolution and the 1.024-ms outputs. The timer can be used to measure the duration of an event under firmware control by reading the timer at the start and at the end of an event, then calculating the difference between the two values. Clocks A 12-MHz crystal (30-ppm or better) is directly connected between XTAL and GND without the need for external capacitors. A digital clock out function is provided, with selectable output frequencies of 0.75, 1.5, 3, 6, or 12 MHz. This output may be used to clock an external microcontroller (MCU) or ASIC. This output is enabled by default, but may be disabled. Below are the requirements for the crystal to be directly connected to XTAL pin and GND: Power Management The operating voltage of the device is 1.8V to 3.6V DC, which is applied to the VBAT pin. The device can be shut down to a fully static sleep mode by writing to the FRC END = 1 and END STATE = 000 bits in the XACT_CFG_ADR register over the SPI interface. The device will enter sleep mode within 35 s after the last SCK positive edge at the end of this SPI transaction. Alternatively, the device may be configured to automatically enter sleep mode after completing packet transmission or reception. When in sleep mode, the on-chip oscillator is stopped, but the SPI interface remains functional. The device will wake from sleep mode automatically when the device is commanded to enter transmit or receive mode. When resuming from sleep mode, there is a short delay while the oscillator restarts. The device may be configured to assert the IRQ pin when the oscillator has stabilized. The output voltage (VREG) of the Power Management Unit (PMU) is configurable to several minimum values between 2.4V and 2.7V. VREG may be used to provide up to 15 mA (average load) to external devices. It is possible to disable the PMU, and to provide an externally regulated DC supply voltage to the device in the range 2.4V to 3.6V. The PMU also provides a regulated 1.8V supply to the logic. The PMU has been designed to provide high boost efficiency (74-85% depending on input voltage, output voltage and load) when using a Schottky diode and power inductor, eliminating the need for an external boost converter in many systems where other components require a boosted voltage. However, reasonable efficiencies (69-82% depending on input voltage, output voltage and load) may be achieved when using low-cost components such as SOT23 diodes and 0805 inductors. The PMU also provides a configurable low battery detection function which may be read over the SPI interface. One of seven thresholds between 1.8V and 2.7V may be selected. The interrupt pin may be configured to assert when the voltage on the VBAT pin falls below the configured threshold. LV IRQ is not a latched event. Battery monitoring is disabled when the device is in sleep mode. Nominal Frequency: 12 MHz Operating Mode: Fundamental Mode Resonance Mode: Parallel Resonant Frequency Initial Stability: 30 ppm Series Resistance: <60 ohms Load Capacitance: 10 pF Drive Level: l00 W The MCU function features an internal oscillator. The clock generator provides the 12-MHz and 24-MHz clocks that remain internal to the microcontroller. GPIO Interface The MCU function features up to 15 general-purpose IO (GPIO) pins.The IO pins are grouped into three ports (Port 0 to 2). The pins on Port 0 and Port 1 may each be configured individually while the pins on Port 2 may only be configured as a group. Each GPIO port supports high-impedance inputs, configurable pull up, open drain output, CMOS/TTL inputs, and CMOS output with up to two pins that support programmable drive strength of up to 50-mA sink current. Additionally, each IO pin can be used to generate a GPIO interrupt to the microcontroller. Each GPIO port has its own GPIO interrupt vector with the exception of GPIO Port 0. GPIO Port 0 has three dedicated pins that have independent interrupt vectors (P0.1, P0.3-P0.4). Document #: 001-07611 Rev *C Page 8 of 65 [+] Feedback CYRF69103 The following three figures show different examples of how to use PRoC LP with and without the PMU. Figure 3 shows the most common circuit making use of the PMU to boost battery voltage up to 2.7v. Figure 4. is an example of the circuit used when the supply voltage will always be above 2.7V. This could be three 1.5v battery cells in series along with a linear regulator, or some similar power source. Figure 5 shows an example of using the PRoC LP with its PMU disabled and an external boost to supply power to the device. This might be required when the load is much greater than the 15 mA average load that PRoC can support. Figure 3. PMU Enabled Figure 4. PMU Disabled - Linear Regulator VCC 0.047F 0.047F 0.047F 0.047F 0.047F 0.047F 0.047F 0.047F VBat 1 1% 10F 6.3V 1F 6.3V VCC VBat2 VBat0 VCC1 VCC2 VBat1 0.047F 0.047F 0.047F 0.047F 0.047F _ VDD VDD_MICRO PRoC LP 0.047F 0.1F L/D VBat2 VBat1 VBat0 VReg VCC1 VCC2 VCC3 VIO VDD VDD_MICRO Figure 5. PMU Disabled - External Boost Converter PRoC LP VCC VCC3 V Bat 0.047F VIO VReg External DC-DC Boost Converter 0.1F L/D 1 Ohm 1% 10F 6.3V 1F 6.3V 0.047F 0.047F 0.047F 0.047F 47 Ohm VBat 10nH BAT400D VCC 100F 10V 10F6.3V 0.047F VBat2 VBat0 VCC1 VCC2 VDD VDD_MICRO VBat1 PRoC LP 0.1F L/D Document #: 001-07611 Rev *C Page 9 of 65 VCC3 VReg VIO [+] Feedback CYRF69103 Low Noise Amplifier (LNA) and Received Signal Strength Indication (RSSI) The gain of the receiver may be controlled directly by clearing the AGC EN bit and writing to the Low Noise Amplifier (LNA) bit of the RX_CFG_ADR register. When the LNA bit is cleared, the receiver gain is reduced by approximately 20 dB, allowing accurate reception of very strong received signals (for example when operating a receiver very close to the transmitter). An additional 20 dB of receiver attenuation can be added by setting the Attenuation (ATT) bit; this allows data reception to be limited to devices at very short ranges. Disabling AGC and enabling LNA is recommended unless receiving from a device using external PA. The RSSI register returns the relative signal strength of the on-channel signal power. When receiving, the device may be configured to automatically measure and store the relative strength of the signal being received as a 5-bit value. When enabled, an RSSI reading is taken and may be read through the SPI interface. An RSSI reading is taken automatically when the start of a packet is detected. In addition, a new RSSI reading is taken every time the previous reading is read from the RSSI register, allowing the background RF energy level on any given channel to be easily measured when RSSI is read when no signal is being received. A new reading can occur as fast as once every 12 s. Figure 6. 3-Wire SPI Mode MOSI SCK nSS MCU Function P1.5/MOSI MOSI/MISO multiplexed on one MOSI pin Radio Function MOSI P1.4/SCK SCK P1.3/nSS nSS 4-Wire SPI Interface The 4-wire SPI communications interface consists of MOSI, MISO, SCK, and SS. The device receives SCK from the MCU function on the SCK pin. Data from the MCU function is shifted in on the MOSI pin. Data to the MCU function is shifted out on the MISO pin. The active low SS pin must be asserted for the two functions to communicate. The IRQ function may be optionally multiplexed with the MOSI pin; when this option is enabled the IRQ function is not available while the SS pin is low. When using this configuration, user firmware should ensure that the MOSI function on MCU function is in a high-impedance state whenever SS is high. Figure 7. 4-Wire SPI Mode MOSI SCK nSS SPI Interface The SPI interface between the MCU function and the radio function is a 3-wire SPI Interface. The three pins are MOSI (Master Out Slave In), SCK (Serial Clock), SS (Slave Select). There is an alternate 4-wire MISO Interface that requires the connection of two external pins. The SPI interface is controlled by configuring the SPI Configure Register. (SPICR Addr: 0x3D). 3-Wire SPI Interface The radio function receives a clock from the MCU function on the SCK pin. The MOSI pin is multiplexed with the MISO pin. Bidirectional data transfer takes place between the MCU function and the radio function through this multiplexed MOSI pin. When using this mode the user firmware should ensure that the MOSI pin on the MCU function is in a high impedance state, except when the MCU is actively transmitting data. Firmware must also control the direction of data flow and switch directions between MCU function and radio function by setting the SWAP bit [Bit 7] of the SPI Configure Register. The SS pin is asserted prior to initiating a data transfer between the MCU function and the radio function. The IRQ function may be optionally multiplexed with the MOSI pin; when this option is enabled the IRQ function is not available while the SS pin is low. When using this configuration, user firmware should ensure that the MOSI function on MCU function is in a high-impedance state whenever SS is high. MCU Function Radio Function P1.5/MOSI MOSI P1.6/MISO P1.4/SCK SCK MISO P1.3/nSS nSS This connection is external to the PRoC LP Chip Document #: 001-07611 Rev *C Page 10 of 65 [+] Feedback CYRF69103 SPI Communication and Transactions The SPI transactions can be single byte or multi-byte. The MCU function initiates a data transfer through a Command/Address byte. The following bytes are data bytes. The SPI transaction format is shown in Figure 4. The DIR bit specifies the direction of data transfer. 0 = Master reads from slave. 1 = Master writes to slave. The INC bit helps to read or write consecutive bytes from contiguous memory locations in a single burst mode operation. If Slave Select is asserted and INC = 1, then the master MCU function reads a byte from the radio, the address is incremented by a byte location, and then the byte at that location is read, and so on. If Slave Select is asserted and INC = 0, then the MCU function reads/writes the bytes in the same register in burst mode, but if it is a register file then it reads/writes the bytes in that register file. Table 4. SPI Transaction Format Byte 1 Bit # Bit Name 7 DIR 6 INC [5:0] Address The SPI interface between the radio function and the MCU is not dependent on the internal 12-MHz oscillator of the radio. Therefore, radio function registers can be read from or written into while the radio is in sleep mode. SPI IO Voltage References The SPI interfaces between MCU function and the radio and the IRQ and RST have a separate voltage reference VIO. For CYRF69103 VIO is normally set to VCC. SPI Connects to External Devices The three SPI wires, MOSI, SCK, and SS are also drawn out of the package as external pins to allow the user to interface their own external devices (such as optical sensors and others) through SPI. The radio function also has its own SPI wires MISO and IRQ, which can be used to send data back to the MCU function or send an interrupt request to the MCU function. They can also be configured as GPIO pins. Byte 1+N [7:0] Data The Accumulator Register (CPU_A) is the general-purpose register that holds the results of instructions that specify any of the source addressing modes. The Index Register (CPU_X) holds an offset value that is used in the indexed addressing modes. Typically, this is used to address a block of data within the data memory space. The Stack Pointer Register (CPU_SP) holds the address of the current top-of-stack in the data memory space. It is affected by the PUSH, POP, LCALL, CALL, RETI, and RET instructions, which manage the software stack. It can also be affected by the SWAP and ADD instructions. The Flag Register (CPU_F) has three status bits: Zero Flag bit [1]; Carry Flag bit [2]; Supervisory State bit [3]. The Global Interrupt Enable bit [0] is used to globally enable or disable interrupts. The user cannot manipulate the Supervisory State status bit [3]. The flags are affected by arithmetic, logic, and shift operations. The manner in which each flag is changed is dependent upon the instruction being executed (for example, AND, OR, XOR). See Table 22. CPU Architecture This family of microcontrollers is based on a high-performance, 8-bit, Harvard architecture microprocessor. Five registers control the primary operation of the CPU core. These registers are affected by various instructions, but are not directly accessible through the register space by the user. Table 5. CPU Registers and Register Name Register Flags Program Counter Accumulator Stack Pointer Index Register Name CPU_F CPU_PC CPU_A CPU_SP CPU_X The 16-bit Program Counter Register (CPU_PC) allows for direct addressing of the full eight Kbytes of program memory space. Document #: 001-07611 Rev *C Page 11 of 65 [+] Feedback CYRF69103 CPU Registers Flags Register The Flags Register can only be set or reset with logical instruction. Table 6. CPU Flags Register (CPU_F) [R/W] Bit # Field Read/Write Default Bits 7:5 Bit 4 - 0 7 6 Reserved - 0 - 0 5 4 XIO R/W 0 3 Super R 0 2 Carry RW 0 1 Zero RW 1 0 Global IE RW 0 Reserved XIO Set by the user to select between the register banks 0 = Bank 0 1 = Bank 1 Bit 3 Super Indicates whether the CPU is executing user code or Supervisor Code. (This code cannot be accessed directly by the user.) 0 = User Code 1 = Supervisor Code Bit 2 Carry Set by CPU to indicate whether there has been a carry in the previous logical/arithmetic operation 0 = No Carry 1 = Carry Bit 1 Zero Set by CPU to indicate whether there has been a zero result in the previous logical/arithmetic operation 0 = Not Equal to Zero 1 = Equal to Zero Bit 0 Global IE Determines whether all interrupts are enabled or disabled 0 = Disabled 1 = Enabled Note This register is readable with explicit address 0xF7. The OR F, expr and AND F, expr must be used to set and clear the CPU_F bits Accumulator Register Table 7. CPU Accumulator Register (CPU_A) Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 - 0 3 - 0 2 - 0 1 - 0 0 - 0 CPU Accumulator [7:0] Bits 7:0 CPU Accumulator [7:0] 8-bit data value holds the result of any logical/arithmetic instruction that uses a source addressing mode Document #: 001-07611 Rev *C Page 12 of 65 [+] Feedback CYRF69103 Index Register Table 8. CPU X Register (CPU_X) Bit # Field Read/Write Default - 0 - 0 - 0 - 0 7 6 5 4 X [7:0] - 0 - 0 - 0 - 0 3 2 1 0 Bits 7:0 X [7:0] 8-bit data value holds an index for any instruction that uses an indexed addressing mode Stack Pointer Register Table 9. CPU Stack Pointer Register (CPU_SP) Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 - 0 3 - 0 2 - 0 1 - 0 0 - 0 Stack Pointer [7:0] Bits 7:0 Stack Pointer [7:0] 8-bit data value holds a pointer to the current top-of-stack CPU Program Counter High Register Table 10. CPU Program Counter High Register (CPU_PCH) Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 - 0 3 - 0 2 - 0 1 - 0 0 - 0 Program Counter [15:8] Bits 7:0 Program Counter [15:8] 8-bit data value holds the higher byte of the program counter CPU Program Counter Low Register Table 11. CPU Program Counter Low Register (CPU_PCL) Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 - 0 3 - 0 2 - 0 1 - 0 0 - 0 Program Counter [7:0] Bit 7:0 Program Counter [7:0] 8-bit data value holds the lower byte of the program counter Document #: 001-07611 Rev *C Page 13 of 65 [+] Feedback CYRF69103 Addressing Modes Examples of the different addressing modes are discussed in this section and example code is given. Source Indexed The result of an instruction using this addressing mode is placed in either the A register or the X register, which is specified as part of the instruction opcode. Operand 1 is added to the X register forming an address that points to a location in either the RAM memory space or the register space that is the source for the instruction. Arithmetic instructions require two sources; the second source is the A register or X register specified in the opcode. Instructions using this addressing mode are two bytes in length. Table 14. Source Indexed Opcode Operand 1 Instruction Examples ADD A, Operand 1 Source Index Source Immediate The result of an instruction using this addressing mode is placed in the A register, the F register, the SP register, or the X register, which is specified as part of the instruction opcode. Operand 1 is an immediate value that serves as a source for the instruction. Arithmetic instructions require two sources. Instructions using this addressing mode are two bytes in length. Table 12. Source Immediate Opcode Instruction Examples ADD A, Immediate Value [X+7] 7 ;In this case, the immediate value ;of 7 is added with the Accumulator, ;and the result is placed in the ;Accumulator. ;In this case, the immediate value ;of 8 is moved to the X register. ;In this case, the immediate value ;of 9 is logically ANDed with the F ;register and the result is placed ;in the F register. MOV X, REG[X+8] ;In this case, the value in ;the memory location at ;address X + 7 is added with ;the Accumulator, and the ;result is placed in the ;Accumulator. ;In this case, the value in ;the register space at ;address X + 8 is moved to ;the X register. MOV X, 8 AND F, 9 Destination Direct The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is an address that points to the location of the result. The source for the instruction is either the A register or the X register, which is specified as part of the instruction opcode. Arithmetic instructions require two sources; the second source is the location specified by Operand 1. Instructions using this addressing mode are two bytes in length. Table 15. Destination Direct Opcode Instruction Examples ADD [7], Operand 1 Destination Address Source Direct The result of an instruction using this addressing mode is placed in either the A register or the X register, which is specified as part of the instruction opcode. Operand 1 is an address that points to a location in either the RAM memory space or the register space that is the source for the instruction. Arithmetic instructions require two sources; the second source is the A register or X register specified in the opcode. Instructions using this addressing mode are two bytes in length. Table 13. Source Direct Opcode Instruction Examples ADD A, Operand 1 Source Address A [7] ;In this case, the value in ;the RAM memory location at ;address 7 is added with the ;Accumulator, and the result ;is placed in the Accumulator. ;In this case, the value in ;the memory location at ;address 7 is added with the ;Accumulator, and the result ;is placed in the memory ;location at address 7. The ;Accumulator is unchanged. ;In this case, the ;Accumulator is moved to the ;register space location at ;address 8. The Accumulator ;is unchanged. MOV REG[8], A MOV X, REG[8] ;In this case, the value in ;the register space at address ;8 is moved to the X register. Document #: 001-07611 Rev *C Page 14 of 65 [+] Feedback CYRF69103 Destination Indexed The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is added to the X register forming the address that points to the location of the result. The source for the instruction is the A register. Arithmetic instructions require two sources; the second source is the location specified by Operand 1 added with the X register. Instructions using this addressing mode are two bytes in length. Table 16. Destination Indexed Opcode Instruction Example ADD [X+7], Operand 1 Destination Index Destination Indexed Source Immediate The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is added to the X register to form the address of the result. The source for the instruction is Operand 2, which is an immediate value. Arithmetic instructions require two sources; the second source is the location specified by Operand 1 added with the X register. Instructions using this addressing mode are three bytes in length. Table 18. Destination Indexed Source Immediate Opcode Instruction Operand 1 Destination Index Operand 2 Immediate Value A ;In this case, the value in the ;memory location at address X+7 ;is added with the Accumulator, ;and the result is placed in ;the memory location at address ;x+7. The Accumulator is ;unchanged. Examples ADD [X+7], 5 ;In this case, the value in ;the memory location at ;address X+7 is added with ;the immediate value of 5 ;and the result is placed in ;the memory location at ;address X+7. ;In this case, the ;immediate value of 6 is ;moved into the location in ;the register space at ;address X+8. MOV REG[X+8], 6 Destination Direct Source Immediate The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is the address of the result. The source for the instruction is Operand 2, which is an immediate value. Arithmetic instructions require two sources; the second source is the location specified by Operand 1. Instructions using this addressing mode are three bytes in length. Table 17. Destination Direct Source Immediate Opcode Instruction Examples ADD [7], Operand 1 Destination Address Operand 2 Immediate Value Destination Direct Source Direct The result of an instruction using this addressing mode is placed within the RAM memory. Operand 1 is the address of the result. Operand 2 is an address that points to a location in the RAM memory that is the source for the instruction. This addressing mode is only valid on the MOV instruction. The instruction using this addressing mode is three bytes in length. Table 19. Destination Direct Source Direct 5 ;In this case, value in the ;memory location at address 7 is ;added to the immediate value of ;5, and the result is placed in ;the memory location at address 7. ;In this case, the immediate ;value of 6 is moved into the ;register space location at ;address 8. Opcode Instruction Operand 1 Destination Address Operand 2 Source Address MOV REG[8], 6 Example MOV [7], [8] ;In this case, the value in the ;memory location at address 8 is ;moved to the memory location at ;address 7. Document #: 001-07611 Rev *C Page 15 of 65 [+] Feedback CYRF69103 Source Indirect Post Increment The result of an instruction using this addressing mode is placed in the Accumulator. Operand 1 is an address pointing to a location within the memory space, which contains an address (the indirect address) for the source of the instruction. The indirect address is incremented as part of the instruction execution. This addressing mode is only valid on the MVI instruction. The instruction using this addressing mode is two bytes in length. Refer to the PSoC Designer: Assembly Language User Guide for further details on MVI instruction. Table 20. Source Indirect Post Increment Opcode Instruction Example MVI A, Operand 1 Source Address Address Destination Indirect Post Increment The result of an instruction using this addressing mode is placed within the memory space. Operand 1 is an address pointing to a location within the memory space, which contains an address (the indirect address) for the destination of the instruction. The indirect address is incremented as part of the instruction execution. The source for the instruction is the Accumulator. This addressing mode is only valid on the MVI instruction. The instruction using this addressing mode is two bytes in length. Table 21. Destination Indirect Post Increment Opcode Instruction Example MVI [8], A Operand 1 Destination Address Address [8] ;In this case, the value in the ;memory location at address 8 is ;an indirect address. The memory ;location pointed to by the ;indirect address is moved into the ;Accumulator. The indirect ;address is then incremented. ;In this case, the value in ;the memory location at ;address 8 is an indirect ;address. The Accumulator is ;moved into the memory location ;pointed to by the indirect ;address. The indirect address ;is then incremented. Document #: 001-07611 Rev *C Page 16 of 65 [+] Feedback CYRF69103 Instruction Set Summary The instruction set is summarized in Table 22 numerically and serves as a quick reference. If more information is needed, the Table 22. Instruction Set Summary Sorted Numerically by Opcode Order[1, 2] Opcode Hex Opcode Hex Cycles Cycles Bytes Bytes Instruction Format Flags Instruction Format Instruction Set Summary tables are described in detail in the PSoC Designer Assembly Language User Guide (available on the www.cypress.com web site). Opcode Hex Cycles Flags Bytes Instruction Format Flags 00 15 01 02 03 04 05 06 08 09 0A 0B 0C 0D 0E 10 11 12 13 14 15 16 18 19 1A 1B 1C 1D 1E 20 21 22 23 24 25 26 4 6 7 7 8 9 4 4 6 7 7 8 9 4 4 6 7 7 8 9 5 4 6 7 7 8 9 5 4 6 7 7 8 9 1 2 2 2 2 2 3 3 1 2 2 2 2 2 3 3 1 2 2 2 2 2 3 3 1 2 2 2 2 2 3 3 1 2 2 2 2 2 3 3 1 2 2 2 2 SSC ADD A, expr ADD A, [expr] ADD A, [X+expr] ADD [expr], A ADD [X+expr], A ADD [expr], expr ADD [X+expr], expr PUSH A ADC A, expr ADC A, [expr] ADC A, [X+expr] ADC [expr], A ADC [X+expr], A ADC [expr], expr ADC [X+expr], expr PUSH X SUB A, expr SUB A, [expr] SUB A, [X+expr] SUB [expr], A SUB [X+expr], A SUB [expr], expr SUB [X+expr], expr POP A SBB A, expr SBB A, [expr] SBB A, [X+expr] SBB [expr], A SBB [X+expr], A SBB [expr], expr SBB [X+expr], expr POP X AND A, expr AND A, [expr] AND A, [X+expr] AND [expr], A AND [X+expr], A AND [expr], expr AND [X+expr], expr ROMX OR A, expr OR A, [expr] OR A, [X+expr] OR [expr], A Z Z Z Z Z Z Z Z Z Z Z Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z 2D 2E 30 31 32 33 34 35 36 38 39 3A 3B 3C 3D 8 9 9 4 6 7 7 8 9 5 5 7 8 8 9 2 3 3 1 2 2 2 2 2 3 3 2 2 2 2 3 3 2 2 1 3 3 3 3 3 3 3 3 3 3 1 2 2 1 1 2 2 2 2 2 3 3 2 2 2 OR [X+expr], A OR [expr], expr OR [X+expr], expr HALT XOR A, expr XOR A, [expr] XOR A, [X+expr] XOR [expr], A XOR [X+expr], A XOR [expr], expr XOR [X+expr], expr ADD SP, expr CMP A, expr CMP A, [expr] CMP A, [X+expr] CMP [expr], expr CMP [X+expr], expr MVI A, [ [expr]++ ] MVI [ [expr]++ ], A NOP AND reg[expr], expr AND reg[X+expr], expr OR reg[expr], expr OR reg[X+expr], expr XOR reg[expr], expr XOR reg[X+expr], expr TST [expr], expr TST [X+expr], expr TST reg[expr], expr TST reg[X+expr], expr SWAP A, X SWAP A, [expr] SWAP X, [expr] SWAP A, SP MOV X, SP MOV A, expr MOV A, [expr] MOV A, [X+expr] MOV [expr], A MOV [X+expr], A MOV [expr], expr MOV [X+expr], expr MOV X, expr MOV X, [expr] MOV X, [X+expr] Z Z Z Z Z Z Z Z Z Z 5A 5B 5C 5D 5E 60 61 62 63 64 65 5 4 4 6 7 5 6 8 9 4 7 8 4 7 8 4 7 8 4 7 8 4 4 4 4 4 4 7 8 4 4 7 8 7 8 5 11 5 5 5 5 7 2 1 1 2 2 3 2 2 3 3 1 2 2 1 2 2 1 2 2 1 2 2 2 2 2 1 1 1 2 2 1 1 2 2 3 3 1 1 2 2 2 2 2 2 2 2 MOV [expr], X MOV A, X MOV X, A MOV A, reg[expr] MOV A, reg[X+expr] MOV [expr], [expr] MOV reg[expr], A MOV reg[X+expr], A MOV reg[expr], expr MOV reg[X+expr], expr ASL A ASL [expr] ASL [X+expr] ASR A ASR [expr] ASR [X+expr] RLC A RLC [expr] RLC [X+expr] RRC A RRC [expr] RRC [X+expr] AND F, expr OR F, expr XOR F, expr CPL A INC A INC X INC [expr] INC [X+expr] DEC A DEC X DEC [expr] DEC [X+expr] LCALL LJMP RETI RET JMP CALL JZ JNZ JC JNC JACC INDEX Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z Z Z 2F 10 5F 10 07 10 37 10 if (A=B) Z=1 66 if (A 3E 10 3F 10 40 41 43 45 47 48 49 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 4 9 9 9 8 9 9 5 7 7 5 4 4 5 6 5 6 8 9 4 6 7 42 10 44 10 46 10 17 10 4A 10 1F 10 7C 13 7E 10 27 10 28 11 29 2A 2B 2C 4 6 7 7 Fx 13 Notes 1. Interrupt routines take 13 cycles before execution resumes at interrupt vector table. 2. The number of cycles required by an instruction is increased by one for instructions that span 256-byte boundaries in the Flash memory space. Document #: 001-07611 Rev *C Page 17 of 65 [+] Feedback CYRF69103 Memory Organization Flash Program Memory Organization Figure 8. Program Memory Space with Interrupt Vector Table after reset 16-bit PC Address 0x0000 0x0004 0x0008 0x000C 0x0010 0x0014 0x0018 0x001C 0x0020 0x0024 0x0028 0x002C 0x0030 0x0034 0x0038 0x003C 0x0040 0x0044 0x0048 0x004C 0x0050 0x0054 0x0058 0x005C 0x0060 0x0064 0x0068 Program execution begins here after a reset POR/LVD Reserved SPI Transmitter Empty SPI Receiver Full GPIO Port 0 GPIO Port 1 INT1 Reserved Reserved Reserved Reserved Reserved 1-ms Interval Timer Programmable Interval Timer Reserved Reserved 16-bit Free Running Timer Wrap INT2 Reserved GPIO Port 2 Reserved Reserved Reserved Reserved Sleep Timer Program Memory begins here (if below interrupts not used, program memory can start lower) 0x1FFF Document #: 001-07611 Rev *C Page 18 of 65 [+] Feedback CYRF69103 Data Memory Organization The MCU function provides up to 256 bytes of data RAM Figure 9. Data Memory Organization after reset 8-bit PSP Address 0x00 Stack begins here and grows upward Top of RAM Memory 0xFF a separate memory space from user code. The SROM functions are accessed by executing the Supervisory System Call instruction (SSC), which has an opcode of 00h. Prior to executing the SSC, the M8C's accumulator needs to be loaded with the desired SROM function code from Table 23. Undefined functions will cause a HALT if called from user code. The SROM functions are executing code with calls; therefore, the functions require stack space. With the exception of Reset, all of the SROM functions have a parameter block in SRAM that must be configured before executing the SSC. Table 24 lists all possible parameter block variables. The meaning of each parameter, with regards to a specific SROM function, is described later in this chapter Table 23. SROM Function Codes Function Code 00h 01h 02h 03h 05h 06h 07h Function Name SWBootReset ReadBlock WriteBlock EraseBlock EraseAll TableRead CheckSum Stack Space 0 7 10 9 11 3 3 Flash This section describes the Flash block of the CYRF69103. Much of the user-visible Flash functionality, including programming and security, are implemented in the M8C Supervisory Read Only Memory (SROM). CYRF69103 Flash has an endurance of 1000 cycles and 10-year data retention. Flash Programming and Security All Flash programming is performed by code in the SROM. The registers that control the Flash programming are only visible to the M8C CPU when it is executing out of SROM. This makes it impossible to read, write, or erase the Flash by bypassing the security mechanisms implemented in the SROM. Customer firmware can only program the Flash via SROM calls. The data or code images can be sourced by way of any interface with the appropriate support firmware. This type of programming requires a `boot-loader'--a piece of firmware resident on the Flash. For safety reasons this boot-loader should not be over written during firmware rewrites. The Flash provides four auxiliary rows that are used to hold Flash block protection flags, boot time calibration values, configuration tables, and any device values. The routines for accessing these auxiliary rows are documented in the SROM section. The auxiliary rows are not affected by the device erase function. In-System Programming CYRF69103 enables this type of in-system programming by using the P1.0 and P1.1 pins as the serial programming mode interface. This allows an external controller to cause the CYRF69103 to enter serial programming mode and then to use the test queue to issue Flash access functions in the SROM. SROM The SROM holds code that is used to boot the part, calibrate circuitry, and perform Flash operations (Table 23 lists the SROM functions). The functions of the SROM may be accessed in normal user code or operating from Flash. The SROM exists in Two important variables that are used for all functions are KEY1 and KEY2. These variables are used to help discriminate between valid SSCs and inadvertent SSCs. KEY1 must always have a value of 3Ah, while KEY2 must have the same value as the stack pointer when the SROM function begins execution. This would be the Stack Pointer value when the SSC opcode is executed, plus three. If either of the keys do not match the expected values, the M8C will halt (with the exception of the SWBootReset function). The following code puts the correct value in KEY1 and KEY2. The code starts with a halt, to force the program to jump directly into the setup code and not run into it. Document #: 001-07611 Rev *C Page 19 of 65 [+] Feedback CYRF69103 halt SSCOP: mov [KEY1], 3ah mov X, SP mov A, X add A, 3 mov [KEY2], A Table 24. SROM Function Parameters Variable Name Key1/Counter/Return Code Key2/TMP BlockID Pointer Clock Mode Delay PCL SRAM Address 0,F8h 0,F9h 0,FAh 0,FBh 0,FCh 0,FDh 0,FEh 0,FFh whenever the SROM is entered with an M8C accumulator value of 00h; the SRAM parameter block is not used as an input to the function. This happens, by design, after a hardware reset, because the M8C's accumulator is reset to 00h or when user code executes the SSC instruction with an accumulator value of 00h. The SWBootReset function does not execute when the SSC instruction is executed with a bad key value and a nonzero function code. A CYRF69103 device executes the HALT instruction if a bad value is given for either KEY1 or KEY2. The SWBootReset function verifies the integrity of the calibration data by way of a 16-bit checksum, before releasing the M8C to run user code. ReadBlock Function The ReadBlock function is used to read 64 contiguous bytes from Flash--a block. The first thing this function does is to check the protection bits and determine if the desired BLOCKID is readable. If read protection is turned on, the ReadBlock function exits setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a read failure. If read protection is not enabled, the function will read 64 bytes from the Flash using a ROMX instruction and store the results in SRAM using an MVI instruction. The first of the 64 bytes will be stored in SRAM at the address indicated by the value of the POINTER parameter. When the ReadBlock completes successfully, the accumulator, KEY1 and KEY2, will all have a value of 00h. Table 26. ReadBlock Parameters Name KEY1 KEY2 BLOCKID POINTER Address 0,F8h 0,F9h 0,FAh 0,FBh 3Ah Stack Pointer value, when SSC is executed Flash block number First of 64 addresses in SRAM where returned data should be stored Description The SROM also features Return Codes and Lockouts. Return Codes Return codes aid in the determination of success or failure of a particular function. The return code is stored in KEY1's position in the parameter block. The CheckSum and TableRead functions do not have return codes because KEY1's position in the parameter block is used to return other data. Table 25. SROM Return Codes Return Code 00h 01h 02h 03h Success Function not allowed due to level of protection on block Software reset without hardware reset Fatal error, SROM halted Description WriteBlock Function The WriteBlock function is used to store data in the Flash. Data is moved 64 bytes at a time from SRAM to Flash using this function. The first thing the WriteBlock function does is to check the protection bits and determine if the desired BLOCKID is writable. If write protection is turned on, the WriteBlock function will exit, setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a write failure. The configuration of the WriteBlock function is straightforward. The BLOCKID of the Flash block, where the data is stored, must be determined and stored at SRAM address FAh. The SRAM address of the first of the 64 bytes to be stored in Flash must be indicated using the POINTER variable in the parameter block (SRAM address FBh). Finally, the CLOCK and DELAY values must be set correctly. The CLOCK value determines the length of the write pulse that will be used to store the data in the Flash. The CLOCK and DELAY values are dependent on the CPU. Refer to `Clocking' Section for additional information. Read, write, and erase operations may fail if the target block is read or write protected. Block protection levels are set during device programming. The EraseAll function overwrites data in addition to leaving the entire user Flash in the erase state. The EraseAll function loops through the number of Flash macros in the product, executing the following sequence: erase, bulk program all zeros, erase. After all the user space in all the Flash macros are erased, a second loop erases and then programs each protection block with zeros. SROM Function Descriptions All SROM functions are described in the following sections. SWBootReset Function The SROM function, SWBootReset, is the function that is responsible for transitioning the device from a reset state to running user code. The SWBootReset function is executed Document #: 001-07611 Rev *C Page 20 of 65 [+] Feedback CYRF69103 Table 27. WriteBlock Parameters Name KEY1 KEY2 BLOCK ID Address 0,F8h 0,F9h 0,FAh 3Ah Stack Pointer value, when SSC is executing 8-KB Flash block number (00h-7Fh) 4-KB Flash block number (00h-3Fh) 3-KB Flash block number (00h-2Fh) First 64 addresses in SRAM where the data to be stored in Flash is located prior to calling WriteBlock Clock Divider used to set the write Pulse width For a CPU speed of 12 MHz set to 56h Description bytes of the protection block. Therefore, each protection block byte stores the protection level for four Flash blocks. The bits are packed into a byte, with the lowest numbered block's protection level stored in the lowest numbered bits. The first address of the protection block contains the protection level for blocks 0 through 3; the second address is for blocks 4 through 7. The 64th byte will store the protection level for blocks 252 through 255. Table 29. Protection Modes Mode 00b 01b 10b 11b Settings Description Marketing Unprotected Factory upgrade POINTER 0,FBh SR ER EW IW Unprotected SR ER EW IW Read protect CLOCK DELAY 0,FCh 0,FEh SR ER EW IW Disable external Field upgrade write SR ER EW IW Disable internal write 6 5 4 3 2 Full protection EraseBlock Function The EraseBlock function is used to erase a block of 64 contiguous bytes in Flash. The first thing the EraseBlock function does is to check the protection bits and determine if the desired BLOCKID is writable. If write protection is turned on, the EraseBlock function will exit, setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a write failure. The EraseBlock function is only useful as the first step in programming. Erasing a block will not cause data in a block to be one hundred percent unreadable. If the objective is to obliterate data in a block, the best method is to perform an EraseBlock followed by a WriteBlock of all zeros. To set up the parameter block for the EraseBlock function, correct key values must be stored in KEY1 and KEY2. The block number to be erased must be stored in the BLOCKID variable and the CLOCK and DELAY values must be set based on the current CPU speed. Table 28. EraseBlock Parameters Name KEY1 KEY2 BLOCKID CLOCK DELAY Address 0,F8h 0,F9h 0,FAh 0,FCh 0,FEh 3Ah Stack Pointer value when SSC is executed Flash block number (00h-7Fh) Clock Divider used to set the erase pulse width For a CPU speed of 12 MHz set to 56h EraseAll Function ProtectBlock Function The CYRF69103 device offers Flash protection on a block-by-block basis. Table 29 lists the protection modes available. In the table, ER and EW are used to indicate the ability to perform external reads and writes. For internal writes, IW is used. Internal reading is always permitted by way of the ROMX instruction. The ability to read by way of the SROM ReadBlock function is indicated by SR. The protection level is stored in two bits, according to Table 29. These bits are bit packed into the 64 Document #: 001-07611 Rev *C The EraseAll function performs a series of steps that destroy the user data in the Flash macros and resets the protection block in each Flash macro to all zeros (the unprotected state). The EraseAll function does not affect the three hidden blocks above the protection block in each Flash macro. The first of these four hidden blocks is used to store the protection table for its eight Kbytes of user data. The EraseAll function begins by erasing the user space of the Flash macro with the highest address range. A bulk program of all zeros is then performed on the same Flash macro, to destroy Page 21 of 65 Description 7 1 0 Block n+3 Block n+2 Block n+1 Block n The level of protection is only decreased by an EraseAll, which places zeros in all locations of the protection block. To set the level of protection, the ProtectBlock function is used. This function takes data from SRAM, starting at address 80h, and ORs it with the current values in the protection block. The result of the OR operation is then stored in the protection block. The EraseBlock function does not change the protection level for a block. Because the SRAM location for the protection data is fixed and there is only one protection block per Flash macro, the ProtectBlock function expects very few variables in the parameter block to be set prior to calling the function. The parameter block values that must be set, besides the keys, are the CLOCK and DELAY values. Table 30. ProtectBlock Parameters Name KEY1 KEY2 CLOCK DELAY Address 0,F8h 0,F9h 0,FCh 0,FEh 3Ah Stack Pointer value when SSC is executed Clock Divider used to set the write pulse width For a CPU speed of 12 MHz set to 56h Description [+] Feedback CYRF69103 all traces of the previous contents. The bulk program is followed by a second erase that leaves the Flash macro in a state ready for writing. The erase, program, erase sequence is then performed on the next lowest Flash macro in the address space if it exists. Following the erase of the user space, the protection block for the Flash macro with the highest address range is erased. Following the erase of the protection block, zeros are written into every bit of the protection table. The next lowest Flash macro in the address space then has its protection block erased and filled with zeros. The end result of the EraseAll function is that all user data in the Flash is destroyed and the Flash is left in an unprogrammed state, ready to accept one of the various write commands. The protection bits for all user data are also reset to the zero state. The parameter block values that must be set, besides the keys, are the CLOCK and DELAY values. Table 31. EraseAll Parameters Name KEY1 KEY2 CLOCK DELAY Address 0,F8h 0,F9h 0,FCh 0,FEh 3Ah Stack Pointer value when SSC is executed Clock Divider used to set the write pulse width For a CPU speed of 12 MHz set to 56h Description when trim values are read. The BLOCKID value, in the parameter block, is used to indicate which table should be returned to the user. Only the three least significant bits of the BLOCKID parameter are used by the TableRead function for the CYRF69103. The upper five bits are ignored. When the function is called, it transfers bytes from the table to SRAM addresses F8h-FFh. The M8C's A and X registers are used by the TableRead function to return the die's Revision ID. The Revision ID is a 16-bit value hard coded into the SROM that uniquely identifies the die's design. Checksum Function The Checksum function calculates a 16-bit checksum over a user specifiable number of blocks, within a single Flash macro (Bank) starting from block zero. The BLOCKID parameter is used to pass in the number of blocks to calculate the checksum over. A BLOCKID value of 1 will calculate the checksum of only block 0, while a BLOCKID value of 0 will calculate the checksum of all 256 user blocks. The 16-bit checksum is returned in KEY1 and KEY2. The parameter KEY1 holds the lower eight bits of the checksum and the parameter KEY2 holds the upper eight bits of the checksum. The checksum algorithm executes the following sequence of three instructions over the number of blocks times 64 to be checksummed. romx add [KEY1], A adc [KEY2], 0 Table 33. Checksum Parameters Name KEY1 KEY2 BLOCKID Address 0,F8h 0,F9h 0,FAh 3Ah Stack Pointer value when SSC is executed Number of Flash blocks to calculate checksum on Description TableRead Function The TableRead function gives the user access to part specific data stored in the Flash during manufacturing. It also returns a Revision ID for the die (not to be confused with the Silicon ID). Table 32. Table Read Parameters Name KEY1 KEY2 Address 0,F8h 0,F9h 3Ah Stack Pointer value when SSC is executed Table number to read Description BLOCKID 0,FAh Clocking The CYRF69103 internal oscillator outputs two frequencies, the Internal 24 MHz Oscillator and the 32 KHz Low power Oscillator. The Internal 24 MHz Oscillator is designed such that it may be trimmed to an output frequency of 24 MHz over temperature and voltage variation. The Internal 24 MHz Oscillator accuracy is 24 MHz -22% to +10% (between 0-70C). No external components are required to achieve this level of accuracy. Firmware is responsible for selecting the correct trim values from the User row to match the power supply voltage in the end application and writing the values to the trim registers IOSCTR and LPOSCTR. The internal low speed oscillator of nominally 32 KHz provides a slow clock source for the CYRF69103 in suspend mode, particularly to generate a periodic wakeup interrupt and also to provide a clock to sequential logic during power up and power down events when the main clock is stopped. In addition, this oscillator can also be used as a clocking source for the Interval Timer clock (ITMRCLK) and Capture Timer clock (TCAPCLK). The 32 kHz Page 22 of 65 The table space for the CYRF69103 is simply a 64 byte row broken up into eight tables of eight bytes. The tables are numbered zero through seven. All user and hidden blocks in the CYRF69103 consist of 64 bytes. An internal table holds the Silicon ID and returns the Revision ID. The Silicon ID is returned in SRAM, while the Revision ID is returned in the CPU_A and CPU_X registers. The Silicon ID is a value placed in the table by programming the Flash and is controlled by Cypress Semiconductor Product Engineering. The Revision ID is hard coded into the SROM. The Revision ID is discussed in more detail later in this section. An internal table holds alternate trim values for the device and returns a one-byte internal revision counter. The internal revision counter starts out with a value of zero and is incremented each time one of the other revision numbers is not incremented. It is reset to zero each time one of the other revision numbers is incremented. The internal revision count is returned in the CPU_A register. The CPU_X register will always be set to FFh Document #: 001-07611 Rev *C [+] Feedback CYRF69103 Low power Oscillator can operate in low power mode or can provide a more accurate clock in normal mode. The Internal 32 kHz Low power Oscillator accuracy ranges from -53.12% to +56.25%. The 32 KHz low power oscillator can be calibrated against the internal 24 MHz oscillator or another timing source if desired. CYRF69103 provides the ability to load new trim values for the 24 MHz oscillator based on voltage. This allows Vdd to be monitored and have firmware trim the oscillator based on voltage present. The IOSCTR register is used to set trim values for the 24 MHz oscillator. CYRF69103 is initialized with 3.30V trim values at power on, then firmware is responsible for transferring the correct set of trim values to the trim registers to match the application's actual Vdd. The 32 KHz oscillator generally does not require trim adjustments vs. voltage but trim values for the 32 KHz are also stored in Supervisory ROM. Figure 10. SROM Table F8h F9h FAh FBh FCh FDh FEh FFh Table 0 Silicon ID [15-8] Silicon ID [7-0] id g al in V rat n o pe gi O Re Table 1 Table 2 24 MHz IOSCTR @ 3.30V 32 KHz @ 3.30V 32 KHz @ 3.00V 32 KHz @ 2.85V 32 KHz @ 2.70V 24 MHz IOSCTR @ 3.00V 24 MHz IOSCTR @ 2.85V 24 MHz IOSCTR @ 2.70V Table 3 LPOSCTR LPOSCTR LPOSCTR LPOSCTR Table 4 Table 5 Table 6 Table 7 To improve the accuracy of the IMO, new trim values are loaded based on supply voltage to the part. For this, firmware needs to make modifications to two registers: 1. The internal oscillator trim register at location 0x34. 2. The gain register at location 0x38. Trim values for the IOSCTR register: The trim values are stored in SROM tables in the part as shown in Figure 10. The trim values are read out from the part based on voltage settings and written to the IOSCTR register at location 0x34. The pseudo code below shows how this is done. _main: mov mov A, 2 [SSC_BLOCKID], A Document #: 001-07611 Rev *C Page 23 of 65 [+] Feedback CYRF69103 Call SROM operation to read the SROM table (Refer to section SROM Table Read Description) //After this command is executed, the trim values for 3.3, 3.0, 2.85 and 2.7 are stored at locations FC through FF in the RAM. SROM calls are explained in the previous section of this datasheet ; mov A, [FCh] // trim values for 3.3V mov A, [FDh] // trim values for 3.0V ; mov A, [FEh] // trim values for 2.85V ; mov A, [FFh] // trim values for 2.70V mov reg[IOSCTR],A // Loading IOSCTR with trim values for 3.0V .terminate: jmp .terminate SROM Table Read Description The Silicon IDs for CYRF69103 devices are stored in SROM tables in the part, as shown in Figure 10 The Silicon ID can be read out from the part using SROM Table reads. This is demonstrated in the following pseudo code. As mentioned in the section "SROM" on page 19, the SROM variables occupy address F8h through FFh in the SRAM. Each of the variables and their definition in given in the section "SROM" on page 19. AREA SSCParmBlkA(RAM,ABS) org F8h // Variables are defined starting at address F8h ; F8h supervisory key ; F8h result code ;F9h supervisory stack ptr key ; FAh block ID ; FBh pointer to data buffer ; FCh Clock ; FDh ClockW ClockE multiplier ; FEh flash macro sequence delay count 1 ; FFh temporary result code SSC_KEY1: SSC_RETURNCODE: blk 1 SSC_KEY2 : blk 1 SSC_BLOCKID: blk 1 SSC_POINTER: blk 1 SSC_CLOCK: blk 1 SSC_MODE: blk 1 SSC_DELAY: blk 1 SSC_WRITE_ResultCode: blk _main: mov A, 0 mov [SSC_BLOCKID], A// To read from Table 0 - Silicon ID is stored in Table 0 //Call SROM operation to read the SROM table mov X, SP ; copy SP into X mov A, X ; A temp stored in X add A, 3 ; create 3 byte stack frame (2 + pushed A) mov [SSC_KEY2], A ; save stack frame for supervisory code ; load the supervisory code for flash operations mov [SSC_KEY1], 3Ah ;FLASH_OPER_KEY - 3Ah mov Table 23 SSC ; SSC call the supervisory ROM A,6 ; load A with specific operation. 06h is the code for Table read // At the end of the SSC command the silicon ID is stored in F8 (MSB) and F9(LSB) of the SRAM .terminate: jmp .terminate Gain value for the register at location [0x38]: 3.3V = 0x40 3.0V = 0x40 2.85V = 0xFF 2.70V = 0xFF Load register [0x38] with the gain values corresponding to the appropriate voltage. Document #: 001-07611 Rev *C Page 24 of 65 [+] Feedback CYRF69103 Table 34. Oscillator Trim Values vs. Voltage Settings Supervisory ROM Table Table2 FCh Table2 FDh Table2 FEh Table2 FFh Table3 F8h Table3 F9h Table3 FAh Table3 FBh Function 24 MHz IOSCTR at 3.30V 24 MHz IOSCTR at 3.00V 24 MHz IOSCTR at 2.85V 24 MHz IOSCTR at 2.70V 32 kHz LPOSCTRat3.30V 32 kHz LPOSCTRat3.00V 32 kHz LPOSCTRat2.85V 32 kHz LPOSCTRat2.70V sub A, [59h] jz done mov A, [59h] mov X, [58h] sub A, [58h] jz done mov X, [57h] ;;;correct data is in memory location 57h done: mov [57h], X ret The CYRF69103 can optionally be sourced from an external crystal oscillator. The external clock driving on CLKIN range is from 187 KHz to 24 MHz. When using the 32 KHz oscillator the PITMRL/H should be read until two consecutive readings match before sending/receiving data. The following firmware example assumes the developer is interested in the lower byte of the PIT. Read_PIT_counter: mov A, reg[PITMRL] mov [57h], A mov A, reg[PITMRL] mov [58h],A mov [59h], A mov A, reg[PITMRL] mov [60h], A ;;;Start comparison mov A,[60h] mov X, [59h] Table 35. CPU Clock Config (CPUCLKCR) [0x30] [R/W] Bit # Field Read/Write Default Bits 7:1 Bit 0 - 0 - 0 - 0 7 6 5 4 Clock Architecture Description The CYRF69103 clock selection circuitry allows the selection of independent clocks for the CPU, Interval Timers, and Capture Timers. On the CYRF69103, the external oscillator can be sourced by the crystal oscillator, or when the crystal oscillator is disabled it is sourced directly from the CLKIN pin. CPU Clock The CPU clock, CPUCLK, can be sourced from the external crystal oscillator, the Internal 24 MHz Oscillator, or the Internal 32 KHz Low power Oscillator. The selected clock source can optionally be divided by 2n-1 where n is 0-7 (see Table 36). 3 - 0 2 - 0 1 - 0 0 Reserved 0 Reserved - 0 Reserved CPU CLK Select 0 = Internal 24 MHz Oscillator 1 = Reserved to 0 Note The CPU speed selection is configured using the OSC_CR0 Register (Figure 11) Document #: 001-07611 Rev *C Page 25 of 65 [+] Feedback CYRF69103 Table 36. OSC Control 0 (OSC_CR0) [0x1E0] [R/W] Bit # Field Read/Write Default Bits 7:6 Bit 5 - 0 7 Reserved 6 - 0 5 No Buzz R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 CPU Speed [2:0] R/W 0 0 R/W 0 Sleep Timer [1:0] Reserved No Buzz During sleep (the Sleep bit is set in the CPU_SCR Register--Table 40), the LVD and POR detection circuit is turned on periodically to detect any POR and LVD events on the VCC pin (the Sleep Duty Cycle bits in the ECO_TR are used to control the duty cycle--Table 44). To facilitate the detection of POR and LVD events, the No Buzz bit is used to force the LVD and POR detection circuit to be continuously enabled during sleep. This results in a faster response to an LVD or POR event during sleep at the expense of a slightly higher than average sleep current. Obtaining the absolute lowest power usage in sleep mode requires the No Buzz bit be clear 0 = The LVD and POR detection circuit is turned on periodically as configured in the Sleep Duty Cycle 1 = The Sleep Duty Cycle value is overridden. The LVD and POR detection circuit is always enabled Note The periodic Sleep Duty Cycle enabling is independent with the sleep interval shown in the Sleep [1:0] bits below Bits 4:3 Sleep Timer [1:0] Sleep Timer Sleep Timer Clock [1:0] Frequency (Nominal) 00 01 10 512 Hz 64 Hz 8 Hz Sleep Period (Nominal) 1.95 ms 15.6 ms 125 ms Watchdog Period (Nominal) 6 ms 47 ms 375 ms 11 1 Hz 1 sec 3 sec Note Sleep intervals are approximate Bits 2:0 CPU Speed [2:0] The CYRF69103 ma y operate over a range of CPU clock speeds. The reset value for the CPU Speed bits is zero; therefore, the default CPU speed is 3 MHz. CPU Speed [2:0] 000 001 010 011 100 101 110 111 CPU when Internal Oscillator is selected 3 MHz (Default) 6 MHz 12 MHz Reserved 1.5 MHz 750 KHz 187 KHz Reserved External Clock Clock In/8 Clock In/4 Clock In/2 Reserved Clock In/16 Clock In/32 Clock In/128 Reserved Document #: 001-07611 Rev *C Page 26 of 65 [+] Feedback CYRF69103 Table 37. Timer Clock Config (TMRCLKCR) [0x31] [R/W] Bit # Field Read/Write Default Bits 7:6 7 R/W 1 6 R/W 0 5 R/W 0 4 R/W 0 3 R/W 1 2 R/W 1 1 R/W 1 0 R/W 1 TCAPCLK Divider TCAPCLK Select ITMRCLK Divider ITMRCLK Select TCAPCLK Divider [1:0] TCAPCLK Divider controls the TCAPCLK divisor 0 0 = Divider Value 2 0 1 = Divider Value 4 1 0 = Divider Value 6 1 1 = Divider Value 8 Bits 5:4 TCAPCLK Select The TCAPCLK Select field controls the source of the TCAPCLK 0 0 = Internal 24 MHz Oscillator 0 1 =Reserved 1 0 = Internal 32 KHz Low power Oscillator 1 1 = TCAPCLK Disabled Note The 1024 s interval timer is based on the assumption that TCAPCLK is running at 4 MHz. Changes in TCAPCLK frequency will cause a corresponding change in the 1024 s interval timer frequency Bits 3:2 ITMRCLK Divider ITMRCLK Divider controls the ITMRCLK divisor 0 0 = Divider value of 1 0 1 = Divider value of 2 1 0 = Divider value of 3 1 1 = Divider value of 4 Bits 1:0 ITMRCLK Select 0 0 = Internal 24 MHz Oscillator 0 1 = Reserved 1 0 = Internal 32 KHz Low power Oscillator 1 1 = TCAPCLK Note Changing the source of TMRCLK requires that both the source and destination clocks be running. Attempting to change the clock source away from TCAPCLK after that clock has been stopped will not be successful Interval Timer Clock (ITMRCLK) The Interval Timer clock (ITMRCLK) can be sourced from the internal 24 MHz oscillator, the internal 32 kHz low power oscillator, or the timer capture clock. A programmable prescaler of 1, 2, 3, or 4 then divides the selected source. The 12-bit Programmable Interval Timer is a simple down counter with a programmable reload value. It provides a 1 s resolution by default. When the down counter reaches zero, the next clock is spent reloading. The reload value can be read and written while the counter is running, but care should be taken to ensure that the counter does not unintentionally reload while the 12-bit reload value is only partially stored--for example, between the two writes of the 12-bit value. The programmable interval timer generates interrupt to the CPU on each reload. The parameters to be set will appear on the device editor view of PSoC Designer after you place the CYRF69103 timer user module. The parameters are PITIMER_Source and PITIMER_Divider. The PITIMER_Source is the clock to the timer and the PITIMER_Divider is the value the clock is divided by. The interval register (PITMR) holds the value that is loaded into the PIT counter on terminal count. The PIT counter is a down counter. The Programmable Interval Timer resolution is configurable. For example: TCAPCLK divide by x of CPU clock (for example TCAPCLK divide by 2 of a 24 MHz CPU clock will give a frequency of 12 MHz) ITMRCLK divide by x of TCAPCLK (for example, ITMRCLK divide by 3 of TCAPCLK is 4 MHz so resolution is 0.25 s). Timer Capture Clock (TCAPCLK) The Timer Capture clock (TCAPCLK) can be sourced from the external crystal oscillator, internal 24 MHz oscillator or the internal 32 kHz low power oscillator. A programmable prescaler of 2, 4, 6, or 8 then divides the selected source. Document #: 001-07611 Rev *C Page 27 of 65 [+] Feedback CYRF69103 Figure 11. Programmable Interval Timer Block Diagram S y s te m C lo c k C o n fig u ra tio n S ta tu s a n d C o n tro l 1 2 -b it re lo a d v a lu e C lo c k T im e r 1 2 -b it d o w n c o u n te r 1 2 -b it re lo a d c o u n te r In te rru p t C o n tro lle r Internal Clock Trim Table 38. IOSC Trim (IOSCTR) [0x34] [R/W] Bit # Field Read/Write Default R/W 0 7 6 foffset[2:0] R/W 0 R/W 0 R/W D R/W D 5 4 3 2 Gain[4:0] R/W D R/W D R/W D 1 0 The IOSC Calibrate register is used to calibrate the internal oscillator. The reset value is undefined but during boot the SROM writes a calibration value that is determined during manufacturing test. The `D' indicates that the default value is trimmed to 24 MHz at 3.30V at power on Bits 7:5 foffset [2:0] This value is used to trim the frequency of the internal oscillator. These bits are not used in factory calibration and will be zero. Setting each of these bits causes the appropriate fine offset in oscillator frequency foffset bit 0 = 7.5 kHz foffset bit 1 = 15 kHz foffset bit 2 = 30 kHz Bits 4:0 Gain [4:0] The effective frequency change of the offset input is controlled through the gain input. A lower value of the gain setting increases the gain of the offset input. This value sets the size of each offset step for the internal oscillator. Nominal gain change (KHz/offsetStep) at each bit, typical conditions (24 MHz operation) Gain bit 0 = -1.5 kHz Gain bit 1 = -3.0 kHz Gain bit 2 = -6 kHz Gain bit 4 = -24 kHz Document #: 001-07611 Rev *C Page 28 of 65 [+] Feedback CYRF69103 LPOSC Trim Table 39. LPOSC Trim (LPOSCTR) [0x36] [R/W] Bit # Field Read/Write Default 7 32 kHz Low Power R/W 0 6 Reserved - - 5 4 3 2 1 0 32 kHz Bias Trim [1:0] R/W D R/W D R/W D 32 kHz Freq Trim [3:0] R/W D R/W D R/W D This register is used to calibrate the 32 KHz Low speed Oscillator. The reset value is undefined but during boot the SROM writes a calibration value that is determined during manufacturing test. This is the meaning of `D' in the Default field. The trim value can be adjusted vs. voltage as noted in Table 35 Bit 7 32 KHz Low Power 0 = The 32 KHz Low speed Oscillator operates in normal mode 1 = The 32 KHz Low speed Oscillator operates in a low power mode. The oscillator continues to function normally but with reduced accuracy Bit 6 Reserved Bits [5:4] 32 KHz Bias Trim [1:0] These bits control the bias current of the low power oscillator 0 0 = Mid bias 0 1 = High bias 1 0 = Reserved 1 1 = Reserved Important Note Do not program the 32 KHz Bias Trim [1:0] field with the reserved 10b value as the oscillator does not oscillate at all corner conditions with this setting Bits 3:0 32 kHz Freq Trim [3:0] These bits are used to trim the frequency of the low power oscillator CPU Clock During Sleep Mode When the CPU enters sleep mode the CPUCLK Select (Bit [0], Table 35) is forced to the internal oscillator, and the oscillator is stopped. When the CPU comes out of sleep mode it is running on the internal oscillator. The internal oscillator recovery time is three clock cycles of the Internal 32 kHz Low power Oscillator. If the system requires the CPU to run off the external clock after awakening from sleep mode, firmware will need to switch the clock source for the CPU. If the external clock source is the external oscillator and the oscillator is disabled, firmware will need to enable the external oscillator, wait for it to stabilize, and then change the clock source. Reset The microcontroller supports two types of resets: Power on Reset (POR) and Watchdog Reset (WDR). When reset is initiated, all registers are restored to their default states and all interrupts are disabled. The occurrence of a reset is recorded in the System Status and Control Register (CPU_SCR). Bits within this register record the occurrence of POR and WDR Reset respectively. The firmware can interrogate these bits to determine the cause of a reset. The microcontroller resumes execution from Flash address 0x0000 after a reset. The internal clocking mode is active after a reset, until changed by user firmware. Note The CPU clock defaults to 3 MHz (Internal 24 MHz Oscillator divide-by-8 mode) at POR to guarantee operation at the low VCC that might be present during the supply ramp. Document #: 001-07611 Rev *C Page 29 of 65 [+] Feedback CYRF69103 Table 40. System Status and Control Register (CPU_SCR) [0xFF] [R/W] Bit # Field Read/Write Default 7 GIES R 0 6 Reserved - 0 5 WDRS R/C[3] 0 4 PORS R/C[3] 1 3 Sleep R/W 0 2 Reserved - 1 1 Reserved - 0 0 Stop R/W 0 The bits of the CPU_SCR register are used to convey status and control of events for various functions of a CYRF69103 device. Bit 7 GIES The Global Interrupt Enable Status bit is a read-only status bit and its use is discouraged. The GIES bit is a legacy bit, which was used to provide the ability to read the GIE bit of the CPU_F register. However, the CPU_F register is now readable. When this bit is set, it indicates that the GIE bit in the CPU_F register is also set which, in turn, indicates that the microprocessor will service interrupts 0 = Global interrupts disabled 1 = Global interrupt enabled Bit 6 Reserved Bit 5 WDRS The WDRS bit is set by the CPU to indicate that a WDR event has occurred. The user can read this bit to determine the type of reset that has occurred. The user can clear but not set this bit 0 = No WDR 1 = A WDR event has occurred Bit 4 PORS The PORS bit is set by the CPU to indicate that a POR event has occurred. The user can read this bit to determine the type of reset that has occurred. The user can clear but not set this bit 0 = No POR 1 = A POR event has occurred. (Note that WDR events will not occur until this bit is cleared.) Bit 3 SLEEP Set by the user to enable CPU sleep state. CPU will remain in sleep mode until any interrupt is pending. The Sleep bit is covered in more detail in the Sleep Mode section 0 = Normal operation 1 = Sleep Bits 2:1 Reserved Bit 0 STOP This bit is set by the user to halt the CPU. The CPU will remain halted until a reset (WDR, POR, or external reset) has taken place. If an application wants to stop code execution until a reset, the preferred method would be to use the HALT instruction rather than writing to this bit 0 = Normal CPU operation 1 = CPU is halted (not recommended) Power-on Reset POR occurs every time the power to the device is switched on. POR is released when the supply is typically 2.6V for the upward supply transition, with typically 50 mV of hysteresis during the power on transient. Bit 4 of the System Status and Control Register (CPU_SCR) is set to record this event (the register contents are set to 00010000 by the POR). After a POR, the microprocessor is held off for approximately 20 ms for the VCC supply to stabilize before executing the first instruction at address 0x00 in the Flash. If the VCC voltage drops below the POR downward supply trip point, POR is reasserted. The VCC supply needs to ramp linearly from 0 to VCC in 0 to 200 ms. Important The PORS status bit is set at POR and can only be cleared by the user, and cannot be set by firmware. Note 3. C = Clear. This bit can only be cleared by the user and cannot be set by firmware. Watchdog Timer Reset The user has the option to enable the WDT. The WDT is enabled by clearing the PORS bit. When the PORS bit is cleared, the WDT cannot be disabled. The only exception to this is if a POR event takes place, which will disable the WDT. The sleep timer is used to generate the sleep time period and the Watchdog time period. The sleep timer uses the Internal 32 kHz Low power Oscillator system clock to produce the sleep time period. The user can program the sleep time period using the Sleep Timer bits of the OSC_CR0 Register (Table 36). When the sleep time elapses (sleep timer overflows), an interrupt to the Sleep Timer Interrupt Vector will be generated. Document #: 001-07611 Rev *C Page 30 of 65 [+] Feedback CYRF69103 The Watchdog Timer period is automatically set to be three counts of the Sleep Timer overflows. This represents between two and three sleep intervals depending on the count in the Sleep Timer at the previous WDT clear. When this timer reaches three, a WDR is generated. Table 41. Reset Watchdog Timer (RESWDT) [0xE3] [W] Bit # Field Read/Write Default W 0 W 0 W 0 7 6 5 4 W 0 The user can either clear the WDT, or the WDT and the Sleep Timer. Whenever the user writes to the Reset WDT Register (RES_WDT), the WDT will be cleared. If the data that is written is the hex value 0x38, the Sleep Timer will also be cleared at the same time. 3 W 0 2 W 0 1 W 0 0 W 0 Reset Watchdog Timer [7:0] Any write to this register will clear the Watchdog Timer, a write of 0x38 will also clear the Sleep Timer. Bits 7:0 Reset Watchdog Timer [7:0] Sleep Mode The CPU can only be put to sleep by the firmware. This is accomplished by setting the Sleep bit in the System Status and Control Register (CPU_SCR). This stops the CPU from executing instructions, and the CPU will remain asleep until an interrupt comes pending, or there is a reset event (either a Power-on Reset, or a Watchdog Timer Reset). The Low-voltage Detection circuit (LVD) drops into fully functional power reduced states, and the latency for the LVD is increased. The actual latency can be traded against power consumption by changing the Sleep Duty Cycle field of the ECO_TR Register. The Internal 32 KHz Low-speed Oscillator remains running. Prior to entering suspend mode, firmware can optionally configure the 32 KHz Low speed Oscillator to operate in a low power mode to help reduce the overall power consumption (using the 32 KHz Low Power bit, Table 39). This will help save approximately 5 A; however, the trade off is that the 32-KHz Low speed Oscillator will be less accurate (-53.12% to +56.25% deviation). All interrupts remain active. Only the occurrence of an interrupt will wake the part from sleep. The Stop bit in the System Status and Control Register (CPU_SCR) must be cleared for a part to resume out of sleep. The Global Interrupt Enable bit of the CPU Flags Register (CPU_F) does not have any effect. Any unmasked interrupt will wake the system up. As a result, any interrupts not intended for waking should be disabled through the Interrupt Mask Registers. When the CPU enters sleep mode the CPUCLK Select (Bit 1, Table 35) is forced to the Internal Oscillator. The internal oscillator recovery time is three clock cycles of the Internal 32-kHz Low power Oscillator. The Internal 24 MHz Oscillator restarts immediately on exiting Sleep mode. If the external crystal oscillator is used, firmware will need to switch the clock source for the CPU. Unlike the Internal 24 MHz Oscillator, the external oscillator is not automatically shut down during sleep. Systems that need the external oscillator disabled in sleep mode will need to disable the external oscillator prior to entering sleep mode. In systems where the CPU runs off the external oscillator, firmware will need to switch the CPU to the internal oscillator prior to disabling the external oscillator. On exiting sleep mode, when the clock is stable and the delay time has expired, the instruction immediately following the sleep instruction is executed before the interrupt service routine (if enabled). The Sleep interrupt allows the microcontroller to wake up periodically and poll system components while maintaining very low average power consumption. The Sleep interrupt may also be used to provide periodic interrupts during non sleep modes. Sleep Sequence The SLEEP bit is an input into the sleep logic circuit. This circuit is designed to sequence the device into and out of the hardware sleep state. The hardware sequence to put the device to sleep is shown in Figure 12 and is defined as follows. 1. Firmware sets the SLEEP bit in the CPU_SCR0 register. The Bus Request (BRQ) signal to the CPU is immediately asserted. This is a request by the system to halt CPU operation at an instruction boundary. The CPU samples BRQ on the positive edge of CPUCLK. 2. Due to the specific timing of the register write, the CPU issues a Bus Request Acknowledge (BRA) on the following positive edge of the CPU clock. The sleep logic waits for the following negative edge of the CPU clock and then asserts a system-wide Power Down (PD) signal. In Figure 12 the CPU is halted and the system-wide power down signal is asserted. 3. The system-wide PD (power down) signal controls several major circuit blocks: The Flash memory module, the internal 24 MHz oscillator, the EFTB filter and the bandgap voltage reference. These circuits transition into a zero power state. The only operational circuits on chip are the Low Power oscillator, the bandgap refresh circuit, and the supply voltage monitor (POR/LVD) circuit. The external crystal oscillator on CYRF69103 devices is not automatically powered down when the CPU enters the sleep state. Firmware must explicitly disable the external crystal oscillator to reduce power to levels specified. Document #: 001-07611 Rev *C Page 31 of 65 [+] Feedback CYRF69103 Low Power in Sleep Mode To achieve the lowest possible power consumption during suspend or sleep, the following conditions are observed in addition to considerations for the sleep timer and external crystal oscillator: All the other blocks go to the power down mode automatically on suspend. The following steps are user configurable and help in reducing the average suspend mode power consumption. 1. Configure the power supply monitor at a large regular intervals, control register bits are 1,EB[7:6] (Power system sleep duty cycle PSSDC[1:0]). 2. Configure the Low power oscillator into low power mode, control register bit is LOPSCTR[7]. All GPIOs are set to outputs and driven low Clear P11CR[0], P10CR[0] Set P10CR[1] To avoid current consumption make sure ITMRCLK and TCPCLK are not sourced by either low power 32KHz oscillator or 24 MHz crystal-less oscillator. Figure 12. Sleep Timing Firmware write to SCR SLEEP bit causes an immediate BRQ CPU captures BRQ on next CPUCLK edge CPU responds with a BRA On the falling edge of CPUCLK, PD is asserted. The 24/48 MHz system clock is halted; the Flash and bandgap are powered down CPUCLK IOW SLEEP BRQ BRA PD Wakeup Sequence When asleep, the only event that can wake the system up is an interrupt. The global interrupt enable of the CPU flag register does not need to be set. Any unmasked interrupt will wake the system up. It is optional for the CPU to actually take the interrupt after the wakeup sequence. The wakeup sequence is synchronized to the 32 KHz clock for purposes of sequencing a startup delay, to allow the Flash memory module enough time to power up before the CPU asserts the first read access. Another reason for the delay is to allow the oscillator, Bandgap, and LVD/POR circuits time to settle before actually being used in the system. As shown in Figure 13, the wake p sequence is as follows: 1. The wakeup interrupt occurs and is synchronized by the negative edge of the 32 KHz clock. 2. At the following positive edge of the 32 KHz clock, the system-wide PD signal is negated. The Flash memory module, internal oscillator, EFTB, and bandgap circuit are all powered up to a normal operating state. 3. At the following positive edge of the 32 KHz clock, the current values for the precision POR and LVD have settled and are sampled. 4. At the following negative edge of the 32 KHz clock (after about 15 s nominal), the BRQ signal is negated by the sleep logic circuit. On the following CPUCLK, BRA is negated by the CPU and instruction execution resumes. Note that in Figure 13 fixed function blocks, such as Flash, internal oscillator, EFTB, and bandgap, have about 15 s start up. The wakeup times (interrupt to CPU operational) will range from 75 s to 105 s. Document #: 001-07611 Rev *C Page 32 of 65 [+] Feedback CYRF69103 Figure 13. Wakeup Timing S leep Tim er or G P IO interrupt occurs Interrupt is double sam pled by 32K clock and P D is negated to system C P U is restarted after 90 m s (nom inal) C LK32K IN T SLEEP PD BAN D G AP EN ABLE SAM PLE SAM PLE LVD /PO R C PU C LK/ 24M H z BR Q BR A C PU (N ot to Scale) Document #: 001-07611 Rev *C Page 33 of 65 [+] Feedback CYRF69103 Low-Voltage Detect Control Table 42. Low-voltage Control Register (LVDCR) [0x1E3] [R/W] Bit # Field Read/Write Default - 0 7 Reserved - 0 6 5 R/W 0 4 R/W 0 3 Reserved - 0 R/W 0 2 1 VM[2:0] R/W 0 R/W 0 0 PORLEV[1:0] This register controls the configuration of the Power-on Reset/Low-voltage Detection circuit. This register can only be accessed in the second bank of IO space. This requires setting the XIO bit in the CPU flags register. Bits 7:6 Reserved Bits 5:4 PORLEV[1:0] This field controls the level below which the precision power-on-reset (PPOR) detector generates a reset 0 0 = 2.7V Range (trip near 2.6V) 0 1 = 3V Range (trip near 2.9V) 1 0 = Reserved 1 1 = PPOR will not generate a reset, but values read from the Voltage Monitor Comparators Register (Table 43) give the internal PPOR comparator state with trip point set to the 3V range setting. Bit 3 Reserved Bits 2:0 VM[2:0] This field controls the level below which the low-voltage-detect trips--possibly generating an interrupt and the level at which the Flash is enabled for operation. VM[2:0] 000 001 010 011 100 101 110 111 LVD Trip Point (V) Min. 2.69 2.90 3.00 3.10 Max. 2.72 2.94 3.04 3.15 Reserved Reserved Reserved Reserved Typical 2.7 2.92 3.02 3.13 Document #: 001-07611 Rev *C Page 34 of 65 [+] Feedback CYRF69103 POR Compare State Table 43. Voltage Monitor Comparators Register (VLTCMP) [0x1E4] [R] Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 Reserved - 0 - 0 - 0 4 3 2 1 LVD R 0 0 PPOR R 0 This read-only register allows reading the current state of the Low-voltage Detection and Precision-Power-On-Reset comparators Bits 7:2 Reserved Bit 1 LVD This bit is set to indicate that the low-voltage-detect comparator has tripped, indicating that the supply voltage has gone below the trip point set by VM[2:0] (See Table 42.) 0 = No low-voltage-detect event 1 = A low-voltage-detect has tripped Bit 0 PPOR This bit is set to indicate that the precision-power-on-reset comparator has tripped, indicating that the supply voltage is below the trip point set by PORLEV[1:0] 0 = No precision-power-on-reset event 1 = A precision-power-on-reset event has tripped Note This register can only be accessed in the second bank of IO space. This requires setting the XIO bit in the CPU flags register ECO Trim Register Table 44. ECO (ECO_TR) [0x1EB] [R/W] Bit # Field Read/Write Default 7 R/W 0 6 R/W 0 5 - 0 4 - 0 3 Reserved - 0 - 0 - 0 - 0 2 1 0 Sleep Duty Cycle [1:0] This register controls the ratios (in numbers of 32-KHz clock periods) of `on' time versus `off' time for LVD and POR detection circuit Bits 7:6 Sleep Duty Cycle [1:0] 0 0 = 1/128 periods of the Internal 32 kHz Low-speed Oscillator 0 1 = 1/512 periods of the Internal 32 KHz Low-speed Oscillator 1 0 = 1/32 periods of the Internal 32 KHz Low-speed Oscillator 1 1 = 1/8 periods of the Internal 32 KHz Low-speed Oscillator Note This register can only be accessed in the second bank of IO space. This requires setting the XIO bit in the CPU flags register Document #: 001-07611 Rev *C Page 35 of 65 [+] Feedback CYRF69103 General Purpose IO Ports The general purpose IO ports are discussed in the following sections. Port Data Registers Table 45. P0 Data Register (P0DATA)[0x00] [R/W] Bit # Field Read/Write Default 7 P0.7 R/W 0 6 Reserved 5 4 P0.4/INT2 R/W 0 3 P0.3/INT1 R/W 0 2 Reserved R/W 0 1 P0.1 0 Reserved This register contains the data for Port 0. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 0 pins. Bit 7 P0.7 Data Bits 6:5 Reserved Bits 4:3 P0.4-P0.3Data/INT2-INT1 In addition to their use as the P0.4-P0.3 GPIOs, these pins can also be used for the alternative functions as the Interrupt pins (INT1-INT2). To configure the P0.4-P0.3 pins, refer to the P0.3/INT1-P0.4/INT2 Configuration Register (Table 49) Bit 2 Reserved Bit 1 P0.1 Data Bit 0 Reserved Table 46. P1 Data Register (P1DATA) [0x01] [R/W] Bit # Field Read/Write Default 7 P1.7 R/W 0 6 P1.6 R/W 0 5 R/W 0 4 R/W 0 3 P1.3/SSEL R/W 0 2 P1.2 R/W 0 1 P1.1 R/W 0 0 P1.0 R/W - P1.5/SMOSI P1.4/SCLK This register contains the data for Port 1. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 1 pins. Bits 7:6 P1.7- P1.6 Bits 5:3 P1.5-P1.3 Data/SPI Pins (SMISO, SMOSI, SCLK, SSEL) In addition to their use as the P1.6-P1.3 GPIOs, these pins can also be used for the alternative function as the SPI interface pins. To configure the P1.6-P1.3 pins, refer to the P1.3-P1.6 Configuration Register (Table 53) Bits 2:1 P1.2-P1.1 Bit 0 P1.0 Document #: 001-07611 Rev *C Page 36 of 65 [+] Feedback CYRF69103 Table 47. P2 Data Register (P2DATA) [0x02] [R/W] Bit # Field Read/Write Default 7 6 5 Reserved R/W 0 4 3 2 1 P2.1-P2.0 0 R/W 0 This register contains the data for Port 2. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 2 pins Bits 7:2 P2 Data [7:2] Bits 1:0 P2 Data [1:0] GPIO Port Configuration All the GPIO configuration registers have common configuration controls. The following are the bit definitions of the GPIO configuration registers. By default all GPIOs are configured as inputs. To prevent the inputs from floating, the pull up resistors are enabled. Firmware will need to configure each of the GPIOs prior to use. Int Enable When set, the Int Enable bit allows the GPIO to generate interrupts. Interrupt generate can occur regardless of whether the pin is configured for input or output. All interrupts are edge sensitive, however for any interrupt that is shared by multiple sources (that is, Ports 2, 3, and 4) all inputs must be deasserted before a new interrupt can occur. When clear, the corresponding interrupt is disabled on the pin. It is possible to configure GPIOs as outputs, enable the interrupt on the pin and then to generate the interrupt by driving the appropriate pin state. This is useful in test and may have value in applications as well. Int Act Low When clear, the corresponding interrupt is active HIGH. When set, the interrupt is active LOW. For P0.3-P0.4 Int act Low clear causes interrupts to be active on the rising edge. Int act Low set causes interrupts to be active on the falling edge. TTL Thresh When set, the input has TTL threshold. When clear, the input has standard CMOS threshold. Important Note The GPIOs default to CMOS threshold. User's firmware needs to configure the threshold to TTL mode if necessary. High Sink When set, the output can sink up to 50 mA. When clear, the output can sink up to 8 mA. On the CY7C601xx, only the P3.7, P2.7, P0.1, and P0.0 have 50 mA sink drive capability. Other pins have 8 mA sink drive capability. On the CY7C602xx, only the P1.7-P1.3 have 50 mA sink drive capability. Other pins have 8 mA sink drive capability. Open Drain When set, the output on the pin is determined by the Port Data Register. If the corresponding bit in the Port Data Register is set, the pin is in high impedance state. If the corresponding bit in the Port Data Register is clear, the pin is driven LOW. When clear, the output is driven LOW or HIGH. Pull-up Enable When set the pin has a 7K pull up to VDD. When clear, the pull up is disabled. Output Enable When set, the output driver of the pin is enabled. When clear, the output driver of the pin is disabled. For pins with shared functions there are some special cases. P0.0 (CLKIN) and P0.1 (CLKOUT) can not be output enabled when the crystal oscillator is enabled. Output enables for these pins are overridden by XOSC Enable. P1.3 (SSEL), P1.4 (SCLK), P1.5 (SMOSI) and P1.6 (SMISO) can be used for their dedicated functions or for GPIO. To enable the pin for GPIO use, clear the corresponding SPI Use bit or the Output Enable will have no effect. SPI Use The P1.3 (SSEL), P1.4 (SCLK), P1.5 (SMOSI) and P1.6 (SMISO) pins can be used for their dedicated functions or for GPIO. To enable the pin for GPIO, clear the corresponding SPI Use bit. The SPI function controls the output enable for its dedicated function pins when their GPIO enable bit is clear. Document #: 001-07611 Rev *C Page 37 of 65 [+] Feedback CYRF69103 Table 48. P0.1 Configuration (P01CR) [0x06] R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 Reserved 6 Int Enable 5 Int Act Low 4 TTL Thresh 3 High Sink 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register is used to configure P0.1. In the CYRF69103, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit If this pin is used as a general purpose output it will draw current. This pin should be configured as an input to reduce current draw Bit 7 Reserved Table 49. P0.3-P0.4 Configuration (P03CR-P04CR) [0x08-0x09] [R/W] Bit # Field Read/Write Default - 0 - 0 R/W 0 R/W 0 - 0 R/W 0 7 Reserved 6 5 Int Act Low 4 TTL Thresh 3 Reserved 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 These registers control the operation of pins P0.3-P0.4 respectively. These pins are shared between the P0.3-P0.4 GPIOs and the INT1-INT2. The INT1-INT2 interrupts are different than all the other GPIO interrupts. These pins are connected directly to the interrupt controller to provide three edge-sensitive interrupts with independent interrupt vectors. These interrupts occur on a rising edge when Int act Low is clear and on a falling edge when Int act Low is set. These pins are enabled as interrupt sources in the interrupt controller registers (Table 74 and Table 72) To use these pins as interrupt inputs, configure them as inputs by clearing the corresponding Output Enable. If the INT1-INT2 pins are configured as outputs with interrupts enabled, firmware can generate an interrupt by writing the appropriate value to the P0.3, and P0.4 data bits in the P0 Data Register Regardless of whether the pins are used as Interrupt or GPIO pins the Int Enable, Int act Low, TTL Threshold, Open Drain, and Pull-up Enable bits control the behavior of the pin The P0.3/INT1-P0.4/INT2 pins are individually configured with the P03CR (0x08), and P04CR (0x09) respectively Note Changing the state of the Int Act Low bit can cause an unintentional interrupt to be generated. When configuring these interrupt sources, it is best to follow the following procedure: 1. Disable interrupt source 2. Configure interrupt source 3. Clear any pending interrupts from the source 4. Enable interrupt source Table 50. P0.7 Configuration (P07CR) [0x0C] [R/W] Bit # Field Read/Write Default - 0 R/W 0 R/W 0 R/W 0 - 0 R/W 0 7 Reserved 6 Int Enable 5 Int Act Low 4 TTL Thresh 3 Reserved 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register controls the operation of pin P0.7 Document #: 001-07611 Rev *C Page 38 of 65 [+] Feedback CYRF69103 Table 51. P1.1 Configuration (P11CR) [0x0E] [R/W] Bit # Field Read/Write Default - 0 R/W 0 R/W 0 - 0 - 0 R/W 0 - 0 7 Reserved 6 Int Enable 5 Int Act Low 4 Reserved 3 2 Open Drain 1 Reserved 0 Output Enable R/W 0 This register controls the operation of the P1.1 pin The pull-up resistor on this pin is enabled by the P10CR Register Note There is no 2 mA sourcing capability on this pin. The pin can only sink 5 mA at VOL3 section Table 52. P1.2 Configuration (P12CR) [0x0F] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 CLK Output 6 Int Enable 5 Int Act Low 4 TTL Threshold R/W 0 3 Reserved - 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register controls the operation of the P1.2 Bit 7 CLK Output 0 = The internally selected clock is not sent out onto P1.2 pin 1 = When CLK Output is set, the internally selected clock is sent out onto P1.2 pin. Table 53. P1.3 Configuration (P13CR) [0x10] [R/W] Bit # Field Read/Write Default - 0 R/W 0 R/W 0 - 0 R/W 0 R/W 0 7 Reserved 6 Int Enable 5 Int Act Low 4 Reserved 3 High Sink 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register controls the operation of the P1.3 pin The P1.3 GPIO's threshold is always set to TTL When the SPI hardware is enabled, the output enable and output state of the pin is controlled by the SPI circuitry. When the SPI hardware is disabled, the pin is controlled by the Output Enable bit and the corresponding bit in the P1 data register Regardless of whether the pin is used as an SPI or GPIO pin the Int Enable, Int act Low, High Sink, Open Drain, and Pull-up Enable control the behavior of the pin 50 mA sink drive capability is available Document #: 001-07611 Rev *C Page 39 of 65 [+] Feedback CYRF69103 Table 54. P1.4-P1.6 Configuration (P14CR-P16CR) [0x11-0x13] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 - 0 R/W 0 R/W 0 7 SPI Use 6 Int Enable 5 Int Act Low 4 Reserved 3 High Sink 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 These registers control the operation of pins P1.4-P1.6, respectively The P1.4-P1.6 GPIO's threshold is always set to TTL When the SPI hardware is enabled, pins that are configured as SPI Use have their output enable and output state controlled by the SPI circuitry. When the SPI hardware is disabled or a pin has its SPI Use bit clear, the pin is controlled by the Output Enable bit and the corresponding bit in the P1 data register Regardless of whether any pin is used as an SPI or GPIO pin the Int Enable, Int act Low, High Sink, Open Drain, and Pull-up Enable control the behavior of the pin The 50 mA sink drive capability is only available in the CY7C602xx. In the CY7C601xx, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit Bit 7 SPI Use 0 = Disable the SPI alternate function. The pin is used as a GPIO 1 = Enable the SPI function. The SPI circuitry controls the output of the pin Important Note for Comm Modes 01 or 10 (SPI Master or SPI Slave, see Table 58) When configured for SPI (SPI Use = 1 and Comm Modes [1:0] = SPI Master or SPI Slave mode), the input/output direction of pins P1.3, P1.5, and P1.6 is set automatically by the SPI logic. However, pin P1.4's input/output direction is NOT automatically set; it must be explicitly set by firmware. For SPI Master mode, pin P1.4 must be configured as an output; for SPI Slave mode, pin P1.4 must be configured as an input Table 55. P1.7 Configuration (P17CR) [0x14] [R/W] Bit # Field Read/Write Default - 0 R/W 0 R/W 0 - 0 R/W 0 R/W 0 7 Reserved 6 Int Enable 5 Int Act Low 4 Reserved 3 High Sink 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register controls the operation of pin P1.7 50 mA sink drive capability is available. The P1.7 GPIO's threshold is always set to TTL Table 56. P2 Configuration (P2CR) [0x15] [R/W] Bit # Field Read/Write Default - 0 R/W 0 R/W 0 R/W 0 R/W 0 R/W 0 7 Reserved 6 Int Enable 5 Int Act Low 4 TTL Thresh 3 High Sink 2 Open Drain 1 Pull-up Enable R/W 0 0 Output Enable R/W 0 This register controls the operation of pins P2.0-P2.1 Document #: 001-07611 Rev *C Page 40 of 65 [+] Feedback CYRF69103 GPIO Configurations for Low Power Mode: To ensure low power mode, unbonded GPIO pins in CYRF69103 must be placed in a non-floating state. The following assembly code snippet shows how this is achieved. This snippet can be added as a part of the initialization routine. //Code Snippet for addressing unbonded GPIOs mov A, 01h mov reg[1Fh],A mov A, 01h mov reg[16h],A // Port3 Configuration register - Enable ouptut mov A, 00h mov reg[03h],A // Asserting P3.0 to P3.7 outputs to '0' //Port 2 configurations mov A,01h mov reg[15h],A //Port 2 Configuration register -Enable output mov A,00h mov reg[02h],A //Asserting P2.0 to P2.7 outputs to `0' mov A, 01h mov reg[05h],A // Port0.0 Configuration register - Enable output mov reg[07h],A // Port0.2 Configuration register - Enable output mov reg[0Ah],A // Port0.5 Configuration register - Enable output mov reg[0Bh],A // Port0.6 Configuration register - Enable output mov A,reg[00h] mov A,00h and A,9Ah mov reg[00h], A // Asserting outputs '0' to pins in port 1 // NOTE: The code fragment in italics is to be used only if your application configures P2.0 and P2.1 as push-pull outputs. When writing to port 0, to access GPIOs P0.1,3,4,7, mask bits 0,2,5,6.Failing to do so will void the low power Document #: 001-07611 Rev *C Page 41 of 65 [+] Feedback CYRF69103 Serial Peripheral Interface (SPI) The SPI Master/Slave Interface core logic runs on the SPI clock domain. The SPI clock is a divider off of the CPUCLK when in Master Mode. SPI is a four-pin serial interface comprised of a clock, an enable, and two data pins Figure 14. SPI Block Diagram Register Block SCK Speed Sel SCK Clock Generation Master/Slave Sel SCK Clock Select SCK_OE SCK Polarity SCK Phase SCK Clock Phase/Polarity Select SCK SCK Little Endian Sel LE_SEL GPIO Block SS_N SS_N SPI State Machine SS_N Data (8 bit) Load Empty Master/Slave Set SCK LE_SEL Shift Buffer MISO/MOSI Crossbar Output Shift Buffer SS_N_OE MISO_OE MISO MOSI_OE MOSI Data (8 bit) Load Full Input Shift Buffer Sclk Output Enable Slave Select Output Enable Master IN, Slave Out OE Master Out, Slave In, OE SCK_OE SS_N_OE MISO_OE MOSI_OE Document #: 001-07611 Rev *C Page 42 of 65 [+] Feedback CYRF69103 SPI Data Register Table 57. SPI Data Register (SPIDATA) [0x3C] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 0 7 6 5 4 SPIData[7:0] R/W R/W 0 R/W 0 R/W 0 R/W 0 3 2 1 0 When read, this register returns the contents of the receive buffer. When written, it loads the transmit holding register. Bits 7:0 SPI Data [7:0] When an interrupt occurs to indicate to firmware that an byte of receive data is available, or the transmitter holding register is empty, firmware has 7 SPI clocks to manage the buffers--to empty the receiver buffer, or to refill the transmit holding register. Failure to meet this timing requirement will result in incorrect data transfer. SPI Configure Register Table 58. SPI Configure Register (SPICR) [0x3D] [R/W] Bit # Field Read/Write Default Bit 7 7 Swap R/W 0 6 LSB First R/W 0 5 R/W 0 4 R/W 0 3 CPOL R/W 0 2 CPHA R/W 0 1 SCLK Select R/W 0 R/W 0 0 Comm Mode Swap 0 = Swap function disabled 1 = The SPI block swaps its use of SMOSI and SMISO. Among other things, this can be useful in implementing single wire SPI-like communications Bit 6 LSB First 0 = The SPI transmits and receives the MSB (Most Significant Bit) first 1 = The SPI transmits and receives the LSB (Least Significant Bit) first Bits 5:4 Comm Mode [1:0] 0 0: All SPI communication disabled 0 1: SPI master mode 1 0: SPI slave mode 1 1: Reserved Bit 3 CPOL This bit controls the SPI clock (SCLK) idle polarity 0 = SCLK idles low 1 = SCLK idles high Bit 2 CPHA The Clock Phase bit controls the phase of the clock on which data is sampled. Table 59 shows the timing for the various combinations of LSB First, CPOL, and CPHA Bits 1:0 SCLK Select This field selects the speed of the master SCLK. When in master mode, SCLK is generated by dividing the base CPUCLK Important Note for Comm Modes 01b or 10b (SPI Master or SPI Slave): When configured for SPI, (SPI Use = 1--Table 54), the input/output direction of pins P1.3, P1.5, and P1.6 is set automatically by the SPI logic. However, pin P1.4's input/output direction is NOT automatically set; it must be explicitly set by firmware. For SPI Master mode, pin P1.4 must be configured as an output; for SPI Slave mode, pin P1.4 must be configured as an input Document #: 001-07611 Rev *C Page 43 of 65 [+] Feedback CYRF69103 Table 59. SPI Mode Timing vs. LSB First, CPOL and CPHA LSB First CPHA 0 0 CPOL 0 SCLK SSEL D AT A X MSB B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LSB Diagram X 0 0 1 SC LK SSEL DAT A X MSB B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LSB X 0 1 0 SC LK SSEL DAT A X MSB B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LS B X 0 1 1 SC L K SSEL D AT A X MS B B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LS B X 1 0 0 SCLK SSEL DAT A X LSB B it 2 B it 3 B it 4 B it 5 B it 6 B it 7 MS B X 1 0 1 SCLK SSEL DAT A X LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB X 1 1 0 SCLK SSEL DAT A X LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB X 1 1 1 SC LK SSEL DAT A X LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB X Document #: 001-07611 Rev *C Page 44 of 65 [+] Feedback CYRF69103 Table 60. SPI SCLK Frequency SCLK CPUCLK Select Divisor 00 01 10 11 6 12 48 96 2 MHz 1 MHz 250 KHz 125 KHz SCLK Frequency when CPUCLK = 12 MHz The 16-bit free-running counter is used as the time-base for timer captures and can also be used as a general time-base by software. Registers Free-Running Counter The 16-bit free-running counter is clocked by a 4 or 6 MHz source. It can be read in software for use as a general purpose time base. When the low order byte is read, the high order byte is registered. Reading the high order byte reads this register allowing the CPU to read the 16-bit value atomically (loads all bits at one time). The free-running timer generates an interrupt at 1024 s rate. It can also generate an interrupt when the free-running counter overflow occurs--every 16.384 ms. This allows extending the length of the timer in software. SPI Interface Pins The SPI interface between the radio function and MCU function uses pins P1.3-P1.5 and optionally P1.6. These pins are configured using the P1.3 and P1.4-P1.6 Configuration. Timer Registers All timer functions of the CYRF69103 are provided by a single timer block. The timer block is asynchronous from the CPU clock. Figure 15. 16-bit Free Running Counter Block Diagram Overflow Interrupt Tim er Capture C lock 16-bit Free Running Counter 1024-s Tim er Interrupt Table 61. Free-Running Timer Low-Order Byte (FRTMRL) [0x20] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 R/W 0 Free-running Timer [7:0] Bits 7:0 Free-running Timer [7:0] This register holds the low order byte of the 16-bit free-running timer. Reading this register causes the high order byte to be moved into a holding register allowing an automatic read of all 16 bits simultaneously For reads, the actual read occurs in the cycle when the low order is read. For writes the actual time the write occurs is the cycle when the high order is written When reading the free-running timer, the low order byte should be read first and the high order second. When writing, the low order byte should be written first then the high order byte Document #: 001-07611 Rev *C Page 45 of 65 [+] Feedback CYRF69103 Table 62. Free-Running Timer High-Order Byte (FRTMRH) [0x21] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 R/W 0 Free-running Timer [15:8] Bits 7:0 Free-running Timer [15:8] When reading the free-running timer, the low order byte should be read first and the high order second. When writing, the low order byte should be written first then the high order byte. Table 63. Programmable Interval Timer Low (PITMRL) [0x26] [R] Bit # Field Read/Write Default R 0 R 0 R 0 7 6 5 4 R 0 3 R 0 2 R 0 1 R 0 0 R 0 Prog Interval Timer [7:0] Bits 7:0 Prog Interval Timer [7:0] This register holds the low order byte of the 12-bit programmable interval timer. Reading this register causes the high order byte to be moved into a holding register allowing an automatic read of all 12 bits simultaneously Table 64. Programmable Interval Timer High (PITMRH) [0x27] [R] Bit # Field Read/Write Default -0 -0 7 6 5 4 3 2 1 0 Reserved -0 -0 R 0 Prog Interval Timer [11:8] R 0 R 0 R 0 Bits 7:4 Reserved Bits 3:0 Prog Internal Timer [11:8] This register holds the high order nibble of the 12-bit programmable interval timer. Reading this register returns the high order nibble of the 12-bit timer at the instant that the low order byte was last read Table 65. Programmable Interval Reload Low (PIRL) [0x28] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 R/W 0 Prog Interval [7:0] Bits 7:0 Prog Interval [7:0] This register holds the lower 8 bits of the timer. While writing into the 12-bit reload register, write lower byte first then the higher nibble. Document #: 001-07611 Rev *C Page 46 of 65 [+] Feedback CYRF69103 Table 66. Programmable Interval Reload High (PIRH) [0x29] [R/W] Bit # Field Read/Write Default -0 -0 7 6 Reserved -0 -0 R/W 0 5 4 3 2 R/W 0 1 R/W 0 0 R/W 0 Prog Interval[11:8] Bits [7:4] Reserved Bits 3:0 Prog Interval [11:8] This register holds the higher 4 bits of the timer. While writing into the 12-bit reload register, write lower byte first then the higher nibble Figure 16. 16-Bit Free-Running Counter Loading Timing Diagram clk_sys write valid addr write data FRT reload ready Clk Timer 12b Prog Timer 12b reload interrupt 12-bit programmable timer load timing Capture timer clk 16b free running counter load 16b free running counter 00A0 00A1 00A2 00A3 00A4 00A5 00A6 00A7 00A8 00A9 00AB 00AC 00AD 00AE 00AF 00B0 00B1 00B2 ACBE ACBF ACC0 16-bit free running counter loading timing Document #: 001-07611 Rev *C Page 47 of 65 [+] Feedback CYRF69103 Figure 17. Memory Mapped Registers Read/Write Timing Diagram clk_sys rd_wrn Valid Addr rdata wdata Memory mapped registers Read/Write timing diagram Interrupt Controller The interrupt controller and its associated registers allow the user's code to respond to an interrupt from almost every functional block in the CYRF69103 devices. The registers associated with the interrupt controller allow interrupts to be disabled either globally or individually. The registers also provide a mechanism by which a user may clear all pending and posted interrupts, or clear individual posted or pending interrupts. The following table lists all interrupts and the priorities that are available in the CYRF69103. Table 67. Interrupt Priorities, Address, Name Interrupt Priority 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Interrupt Address 0000h 0004h 0008h 000Ch 0010h 0014h 0018h 001Ch 0020h 0024h 0028h 002Ch 0030h 0034h 0038h 003Ch 0040h Reset POR/LVD Reserved SPI Transmitter Empty SPI Receiver Full GPIO Port 0 GPIO Port 1 INT1 Reserved Reserved Reserved Reserved Reserved 1 ms Interval timer Programmable Interval Timer Reserved Reserved Name Table 67. Interrupt Priorities, Address, Name (continued) Interrupt Priority 17 18 19 20 21 22 23 24 25 Interrupt Address 0044h 0048h 004Ch 0050h 0054h 0058h 005Ch 0060h 0064h INT2 Reserved GPIO Port 2 Reserved Reserved Reserved Reserved Sleep Timer Name 16-bit Free Running Timer Wrap Architectural Description An interrupt is posted when its interrupt conditions occur. This results in the flip-flop in Figure 18 clocking in a `1'. The interrupt will remain posted until the interrupt is taken or until it is cleared by writing to the appropriate INT_CLRx register. A posted interrupt is not pending unless it is enabled by setting its interrupt mask bit (in the appropriate INT_MSKx register). All pending interrupts are processed by the Priority Encoder to determine the highest priority interrupt which will be taken by the M8C if the Global Interrupt Enable bit is set in the CPU_F register. Disabling an interrupt by clearing its interrupt mask bit (in the INT_MSKx register) does not clear a posted interrupt, nor does it prevent an interrupt from being posted. It simply prevents a posted interrupt from becoming pending. Nested interrupts can be accomplished by reenabling interrupts inside an interrupt service routine. To do this, set the IE bit in the Flag Register. A block diagram of the CYRF69103 Interrupt Controller is shown in Figure 18. Document #: 001-07611 Rev *C Page 48 of 65 [+] Feedback CYRF69103 Figure 18. Interrupt Controller Block Diagram Interrupt Taken or INT_CLRx Write Posted Interrupt Pending Interrupt Priority Encoder Interrupt Vector Interrupt Request M8C Core R 1 Interrupt Source (Timer, GPIO, etc.) INT_MSKx Mask Bit Setting D Q ... ... CPU_F[0] GIE Interrupt Processing The sequence of events that occur during interrupt processing is as follows: 1. An interrupt becomes active, either because: a. The interrupt condition occurs (for example, a timer expires). b. A previously posted interrupt is enabled through an update of an interrupt mask register. c. An interrupt is pending and GIE is set from 0 to 1 in the CPU Flag register. 2. The current executing instruction finishes. 3. The internal interrupt is dispatched, taking 13 cycles. During this time, the following actions occur: a. The MSB and LSB of Program Counter and Flag registers (CPU_PC and CPU_F) are stored onto the program stack by an automatic CALL instruction (13 cycles) generated during the interrupt acknowledge process. b. The PCH, PCL, and Flag register (CPU_F) are stored onto the program stack (in that order) by an automatic CALL instruction (13 cycles) generated during the interrupt acknowledge process. c. The CPU_F register is then cleared. Since this clears the GIE bit to 0, additional interrupts are temporarily disabled. d. The PCH (PC[15:8]) is cleared to zero. e. The interrupt vector is read from the interrupt controller and its value placed into PCL (PC[7:0]). This sets the program counter to point to the appropriate address in the interrupt table (for example, 0004h for the POR/LVD interrupt). 4. Program execution vectors to the interrupt table. Typically, a LJMP instruction in the interrupt table sends execution to the user's Interrupt Service Routine (ISR) for this interrupt. 5. The ISR executes. Note that interrupts are disabled since GIE = 0. In the ISR, interrupts can be re-enabled if desired by setting GIE = 1 (care must be taken to avoid stack overflow). 6. The ISR ends with a RETI instruction which restores the Program Counter and Flag registers (CPU_PC and CPU_F). The restored Flag register re-enables interrupts, since GIE = 1 again. 7. Execution resumes at the next instruction, after the one that occurred before the interrupt. However, if there are more pending interrupts, the subsequent interrupts will be processed before the next normal program instruction. Interrupt Latency The time between the assertion of an enabled interrupt and the start of its ISR can be calculated from the following equation. Latency = Time for current instruction to finish + Time for internal interrupt routine to execute + Time for LJMP instruction in interrupt table to execute. For example, if the 5-cycle JMP instruction is executing when an interrupt becomes active, the total number of CPU clock cycles before the ISR begins would be as follows: (1 to 5 cycles for JMP to finish) + (13 cycles for interrupt routine) + (7 cycles for LJMP) = 21 to 25 cycles. In the example above, at 12 MHz, 25 clock cycles take 2.08 s. Interrupt Registers The Interrupt Registers are discussed it the following sections. Interrupt Clear Register The Interrupt Clear Registers (INT_CLRx) are used to enable the individual interrupt sources' ability to clear posted interrupts. When an INT_CLRx register is read, any bits that are set indicates an interrupt has been posted for that hardware resource. Therefore, reading these registers gives the user the ability to determine all posted interrupts. Document #: 001-07611 Rev *C Page 49 of 65 [+] Feedback CYRF69103 Table 68. Interrupt Clear 0 (INT_CLR0) [0xDA] [R/W] Bit # Field Read/Write Default 7 R/W 0 6 R/W 0 5 INT1 R/W 0 4 R/W 0 3 R/W 0 2 R/W 0 1 Reserved R/W 0 0 POR/LVD R/W 0 GPIO Port 1 Sleep Timer GPIO Port 0 SPI Receive SPI Transmit When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a `1' to the bits and to the ENSWINT (Bit 7 of the INT_MSK3 Register) will post the corresponding hardware interrupt. The GPIO interrupts are edge-triggered. Table 69. Interrupt Clear 1 (INT_CLR1) [0xDB] [R/W] Bit # 7 Reserved Field Read/Write Default 0 R/W 0 6 Prog Interval Timer 5 1 ms Programmable Interrupt R/W 0 - 0 - 0 4 3 2 Reserved 1 0 - 0 - 0 - 0 When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a `1' to the bits AND to the ENSWINT Bit 7 Reserved Table 70. Interrupt Clear 2 (INT_CLR2) [0xDC] [R/W] Bit # 7 Reserved Field Read/Write Default - 0 0 0 R/W 0 - 0 R/W 0 6 Reserved 5 Reserved 4 GPIO Port2 3 Reserved 2 INT2 1 16-bit Counter Wrap R/W 0 0 Reserved 0 When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a `1' to the bits AND to the ENSWINT (Bit 7 of the INT_MSK3 Register) will post the corresponding hardware interrupt Bits 7,6,5,3,0]Reserved Interrupt Mask Registers The Interrupt Mask Registers (INT_MSKx) are used to enable the individual interrupt sources' ability to create pending interrupts. There are four Interrupt Mask Registers (INT_MSK0, INT_MSK1, INT_MSK2, and INT_MSK3), which may be referred to in general as INT_MSKx. If cleared, each bit in an INT_MSKx register prevents a posted interrupt from becoming a pending interrupt (input to the priority encoder). However, an interrupt can still post even if its mask bit is zero. All INT_MSKx bits are independent of all other INT_MSKx bits. If an INT_MSKx bit is set, the interrupt source associated with that mask bit may generate an interrupt that will become a pending interrupt. The Enable Software Interrupt (ENSWINT) bit in INT_MSK3[7] determines the way an individual bit value written to an INT_CLRx register is interpreted. When is cleared, writing 1's to an INT_CLRx register has no effect. However, writing 0's to an INT_CLRx register, when ENSWINT is cleared, will cause the Page 50 of 65 Document #: 001-07611 Rev *C [+] Feedback CYRF69103 corresponding interrupt to clear. If the ENSWINT bit is set, any 0's written to the INT_CLRx registers are ignored. However, 1's written to an INT_CLRx register, while ENSWINT is set, will cause an interrupt to post for the corresponding interrupt. Table 71. Interrupt Mask 3 (INT_MSK3) [0xDE] [R/W] Bit # Field Read/Write Default Bit 7 7 ENSWINT R 0 - 0 - 0 - 0 6 5 4 Software interrupts can aid in debugging interrupt service routines by eliminating the need to create system level interactions that are sometimes necessary to create a hardware-only interrupt. 3 Reserved - 0 2 - 0 1 - 0 0 - 0 Bits 6:0 Enable Software Interrupt (ENSWINT) 0 = Disable. Writing 0's to an INT_CLRx register, when ENSWINT is cleared, will cause the corresponding interrupt to clear 1 = Enable. Writing 1's to an INT_CLRx register, when ENSWINT is set, will cause the corresponding interrupt to post Reserved Table 72. Interrupt Mask 2 (INT_MSK2) [0xDF] [R/W] Bit # 7 Reserved Field Read/Write Default Bit 7: Bit 6: Bit 5: Bit 4: - 0 0 0 R/W 0 - 0 R/W 0 6 Reserved 5 Reserved 4 GPIO Port 2 Int Enable 3 Reserved 2 INT2 Int Enable 1 16-bit Counter Wrap Int Enable R/W 0 0 Reserved 0 Reserved Reserved Reserved GPIO Port 2 Interrupt Enable 0 = Mask GPIO Port 2 interrupt 1 = Unmask GPIO Port 2 interrupt Bit 3: Reserved Bit 2: INT2 Interrupt Enable 0 = Mask INT2 interrupt 1 = Unmask INT2 interrupt Bit 1: 16-bit Counter Wrap Interrupt Enable 0 = Mask 16-bit Counter Wrap interrupt 1 = Unmask 16-bit Counter Wrap interrupt Bit 0: Reserved The GPIO interrupts are edge-triggered. Document #: 001-07611 Rev *C Page 51 of 65 [+] Feedback CYRF69103 Table 73. Interrupt Mask 1 (INT_MSK1) [0xE1] [R/W] Bit # 7 Reserved Field Read/Write Default Bit 7 Bit 6 R/W 0 6 Prog Interval Timer Int Enable R/W 0 5 1 ms Timer Int Enable R/W 0 - 0 - 0 4 3 2 Reserved 1 0 - 0 - 0 - 0 Bit 5 Bit 4:0 Reserved Prog Interval Timer Interrupt Enable 0 = Mask Prog Interval Timer interrupt 1 = Unmask Prog Interval Timer interrupt 1 ms Timer Interrupt Enable 0 = Mask 1 ms interrupt 1 = Unmask 1 ms interrupt Reserved Table 74. Interrupt Mask 0 (INT_MSK0) [0xE0] [R/W] Bit # Field Read/Write Default Bit 7 7 6 5 INT1 Int Enable R/W 0 4 3 2 1 Reserved R/W 0 0 POR/LVD Int Enable R/W 0 GPIO Port 1 Sleep Timer Int Enable Int Enable R/W 0 R/W 0 GPIO Port 0 SPI Receive SPI Transmit Int Enable Int Enable Int Enable R/W 0 R/W 0 R/W 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 GPIO Port 1 Interrupt Enable 0 = Mask GPIO Port 1 interrupt 1 = Unmask GPIO Port 1 interrupt Sleep Timer Interrupt Enable 0 = Mask Sleep Timer interrupt 1 = Unmask Sleep Timer interrupt INT1 Interrupt Enable 0 = Mask INT1 interrupt 1 = Unmask INT1 interrupt GPIO Port 0 Interrupt Enable 0 = Mask GPIO Port 0 interrupt 1 = Unmask GPIO Port 0 interrupt SPI Receive Interrupt Enable 0 = Mask SPI Receive interrupt 1 = Unmask SPI Receive interrupt SPI Transmit Enable 0 = Mask SPI Transmit interrupt 1 = Unmask SPI Transmit interrupt Reserved POR/LVD Interrupt Enable 0 = Mask POR/LVD interrupt 1 = Unmask POR/LVD interrupt Document #: 001-07611 Rev *C Page 52 of 65 [+] Feedback CYRF69103 Interrupt Vector Clear Register Table 75. Interrupt Vector Clear Register (INT_VC) [0xE2] [R/W] Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 R/W 0 3 R/W 0 2 R/W 0 1 R/W 0 0 R/W 0 Pending Interrupt [7:0] The Interrupt Vector Clear Register (INT_VC) holds the interrupt vector for the highest priority pending interrupt when read, and when written will clear all pending interrupts Bits 7:0 Pending Interrupt [7:0] 8-bit data value holds the interrupt vector for the highest priority pending interrupt. Writing to this register will clear all pending interrupts Microcontroller Function Register Summary Addr 00 01 02 06 08-09 0C 0E 0F 10 11-13 14 15 20 21 26 27 28 29 30 Name P0DATA P1DATA P2DATA P01CR P03CR- P04CR P07CR P11CR P12CR P13CR P14CR- P16CR P17CR P2CR FRTMRL FRTMRH PITMRL PITMRH PIRL PIRH CPUCLKCR Reserved Reserved Reserved Prog Interval [7:0] Prog Interval [11:8] CPU CLK Select Reserved to 0. ITMRCLK Divider Gain[4:0] 32-kHz Bias Trim [1:0] SPIData[7:0] Swap LSB First Comm Mode INT1 GPIO Port 0 CPOL SPI Receive CPHA SPI Transmit Reserved GPIO Port 2 Reserved INT2 16-bit Counter Wrap Reserved SCLK Select Reserved POR/LVD 32-kHz Freq Trim [3:0] ITMRCLK Select Reserved Int Enable 7 P0.7 P1.7 6 Reserved 5 Reserved 4 P0.4/INT2 P1.4/SCLK 3 P0.3/INT1 P1.3/SSEL 2 Reserved P1.2 1 P0.1 P1.1 0 Reserved P1.0 R/W b--bb-bbbbbbbb------bb bbbbbbbb --bb-bbb -bbb-bbb -bb--b-b bbbb-bbb -bb-bbbb bbb-bbbb -bb-bbbb -bbbbbbb bbbbbbbb bbbbbbbb rrrrrrrr Prog Interval Timer [11:8] ----rrrr bbbbbbbb ----rrrr -------b Default 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 P1.6/SMISO P1.5/SMOSI Reserved Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low TTL Thresh TTL Thresh TTL Thresh High Sink Reserved Reserved Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain P2.1-P2.0 Pull-up Enable Pull-up Enable Pull-up Enable Reserved Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Reserved Reserved Reserved CLK Output Reserved SPI Use Reserved Reserved Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Reserved TTL Threshold Reserved Reserved Reserved TTL Thresh Reserved High Sink High Sink High Sink High Sink Free-Running Timer [7:0] Free-Running Timer [15:8] Prog Interval Timer [7:0] 31 34 36 3C 3D DA DB DC TMRCLKCR IOSCTR LPOSCTR SPIDATA SPICR TCAPCLK Divider foffset[2:0] 32-kHz Low Power Reserved TCAPCLK Select bbbbbbbb bbbbbbbb 0-bbbbbb bbbbbbbb bbbbbbbb bbbbbb-b -bb-------b-bb- 10001111 000ddddd d-dddddd 00000000 00000000 00000000 00000000 00000000 INT_CLR0 GPIO Port 1 Sleep Timer INT_CLR1 INT_CLR2 Reserved Reserved Prog Interval 1-ms Timer Timer Reserved Reserved Document #: 001-07611 Rev *C Page 53 of 65 [+] Feedback CYRF69103 Microcontroller Function Register Summary (continued) Addr DE DF Name INT_MSK3 INT_MSK2 7 ENSWINT Reserved Reserved Reserved GPIO Port 2 Int Enable 6 5 4 3 Reserved Reserved INT2 Int Enable 16-bit Counter Wrap Int Enable Reserved 2 1 0 R/W r---------b-bbDefault 00000000 00000000 E1 INT_MSK1 Reserved Prog Interval 1-ms Timer Timer Int Enable Int Enable INT1 Int Enable GPIO Port 0 Int Enable SPI Receive Int Enable Reserved -bb----- 00000000 E0 E2 E3 -----F7 FF 1E0 1E3 1EB 1E4 INT_MSK0 GPIO Port 1 Sleep Timer Int Enable Int Enable INT_VC RESWDT CPU_A CPU_X CPU_PCL CPU_PCH CPU_SP CPU_F CPU_SCR OSC_CR0 LVDCR ECO_TR VLTCMP GIES Reserved Reserved SPI Transmit Int Enable Reserved POR/LVD Int Enable bbbbbb-b bbbbbbbb wwwwwww w ------------------------------------ 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000010 00010100 00000000 00000000 00000000 00000000 Pending Interrupt [7:0] Reset Watchdog Timer [7:0] Temporary Register T1 [7:0] X[7:0] Program Counter [7:0] Program Counter [15:8] Stack Pointer [7:0] XIO WDRS No Buzz PORS Super Sleep Carry Reserved Zero Reserved CPU Speed [2:0] VM[2:0] Global IE Stop ---brbbb r-ccb--b --bbbbbb --bb-bbb bb------ Reserved Reserved Sleep Duty Cycle [1:0] Sleep Timer [1:0] Reserved Reserved Reserved PORLEV[1:0] LVD PPOR ------rr Document #: 001-07611 Rev *C Page 54 of 65 [+] Feedback CYRF69103 Radio Function Register Summary Address 0x00 0x01 0x02 0x03 0x04 0x05 0x06 Mnemonic CHANNEL_ADR TX_LENGTH_ADR TX_CTRL_ADR TX_CFG_ADR TX_IRQ_STATUS_ADR RX_CTRL_ADR RX_CFG_ADR 0x07 0x08 0x09 0x0A 0x0B RX_IRQ_STATUS_ADR RX_STATUS_ADR RX_COUNT_ADR RX_LENGTH_ADR PWR_CTRL_ADR b7 Not Used b6 b5 b3 Channel TX Length TXB8 TXB0 IRQEN IRQEN b4 b2 b1 b0 Default[4] -1001000 00000000 00000011 --000101 DATA MODE TXB8 TXB0 TXBERR IRQ IRQ IRQ RXB8 RXB1 RXBERR IRQEN IRQEN IRQEN FAST TURN HILO EN Not Used RXB8 RXB1 RXBERR IRQ IRQ IRQ CRC0 Bad CRC RX Code RX Count RX Length LVI TH PFET disable [10.] TX GO Not Used OS IRQ RX GO AGC EN RXOW IRQ RX ACK TX CLR Not Used LV IRQ RSVD LNA SOPDET IRQ PKT ERR TXB15 IRQEN DATA CODE LENGTH TXB15 IRQ RXB16 IRQEN ATT RXB16 IRQ EOP ERR TXBERR IRQEN TXC IRQEN PA SETTING TXC IRQ RXC IRQEN TXE IRQEN Access[4] -bbbbbbb bbbbbbbb bbbbbbbb --bbbbbb rrrrrrrr bbbbbbbb bbbbb-bb brrrrrrr rrrrrrrr rrrrrrrr rrrrrrrr bbb-bbbb TXE IRQ RXE IRQEN -------00000111 10010-10 RXOW EN VLD EN RXC RXE IRQ IRQ RX Data Mode --------------00000000 00000000 10100000 PMU EN LVIRQ EN PMU Mode Force XSIRQ EN MISO OD PACTL OP FRC END LEN EN Not Used Not Used LNA HINT PMU OUTV 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F 0x26 0x27 0x28 0x29 0x32 0x35 0x39 XTAL_CTRL_ADR IO_CFG_ADR GPIO_CTRL_ADR XACT_CFG_ADR FRAMING_CFG_ADR DATA32_THOLD_ADR DATA64_THOLD_ADR RSSI_ADR EOP_CTRL_ADR [9.] CRC_SEED_LSB_ADR CRC_SEED_MSB_ADR TX_CRC_LSB_ADR TX_CRC_MSB_ADR RX_CRC_LSB_ADR RX_CRC_MSB_ADR TX_OFFSET_LSB_ADR TX_OFFSET_MSB_ADR MODE_OVERRIDE_ADR RX_OVERRIDE_ADR TX_OVERRIDE_ADR XTAL_CFG_ADR CLK_OVERRIDE_ADR CLK_EN_ADR RX_ABORT_ADR AUTO_CAL_TIME_ADR AUTO_CAL_OFFSET_ADR ANALOG_CTRL_ADR XOUT FN IRQ OD IRQ POL XOUT OP MISO OP ACK EN Not Used SOP EN SOP LEN Not Used Not Used Not Used Not Used SOP Not Used HEN Not Used XOUT OD IRQ OP Not Used Not Used FREQ PACTL OD PACTL GPIO SPI 3PIN IRQ GPIO XOUT IP MISO IP PACTL IP IRQ IP END STATE ACK TO SOP TH TH32 TH64 RSSI 000--100 00000000 0000---1-000000 10100101 ----0100 ---01010 0-100000 10100100 00000000 00000000 --------------11111111 11111111 00000000 ----0000 00000--0 000000000000000 bbb--bbb bbbbbbbb bbbbrrrr b-bbbbbb bbbbbbbb ----bbbb ---bbbbb r-rrrrrr bbbbbbbb bbbbbbbb bbbbbbbb rrrrrrrr rrrrrrrr rrrrrrrr rrrrrrrr bbbbbbbb ----bbbb wwwww--w bbbbbbbbbbbbbbb wwwwwww w wwwwwww w wwwwwww w wwwwwww w wwwwwww w wwwwwww w wwwwwww w wwwwwww w rrrrrrrr bbbbbbbb bbbbbbbb bbbbbbbb rrrrrrrr Not Used RSVD ACK RX ACK TX RSVD RSVD RSVD RSVD Not Used RSVD RXTX DLY FRC PRE RSVD RSVD RSVD RSVD Not Used FRC SEN MAN RXACK RSVD RSVD RSVD RSVD ABORT EN EOP CRC SEED LSB CRC SEED MSB CRC LSB CRC MSB CRC LSB CRC MSB STRIM LSB Not Used STRIM MSB FRC AWAKE Not Used Not Used FRC RXDR DIS CRC0 DIS RXCRC ACE MAN TXACK OVRD ACK DIS TXCRC RSVD RSVD START DLY RSVD RSVD RSVD RSVD RSVD RSVD RSVD RSVD RSVD RSVD RSVD RXF RXF RSVD RST Not Used TX INV RSVD RSVD RSVD RSVD 00000000 00000000 00000000 00000000 00000011 00000000 AUTO_CAL_TIME AUTO_CAL_OFFSET RSVD RSVD RSVD RSVD RSVD RSVD RX INV ALL SLOW 00000000 Register Files 0x20 TX_BUFFER_ADR 0x21 0x22 0x23 0x24 0x25 RX_BUFFER_ADR SOP_CODE_ADR DATA_CODE_ADR PREAMBLE_ADR MFG_ID_ADR TX Buffer File RX Buffer File SOP Code File Data Code File Preamble File MFG ID File --------------Note [5] Note [6] Note [7] NA Notes 4. b = read/write; r = read only; w = write only; `-' = not used, default value is undefined. 5. SOP_CODE_ADR default = 0x17FF9E213690C782. 6. DATA_CODE_ADR default = 0x02F9939702FA5CE3012BF1DB0132BE6F. 7. PREAMBLE_ADR default = 0x333302;The count value should be great than 4 for DDR and greater than 8 for SDR 8. Registers must be configured or accessed only when the radio is in IDLE or SLEEP mode.The PMU, GPIOs, RSSI registers can be accessed in Active Tx and Rx mode. 9. EOP_CTRL_ADR[6:4] should never have the value of "000" i.e. EOP Hint Symbol count should never be "0" 10. PFET Bit :Setting this bit to "1" disables the FET, therefore safely allowing Vbat to be connected to a separate reference from Vcc when the PMU is disabled to the radio.om Vcc when the PMU is disabled to the radio. Document #: 001-07611 Rev *C Page 55 of 65 [+] Feedback CYRF69103 All registers are read and writable, except where noted. Registers may be written to or read from either individually or in sequential groups. A single-byte read or write reads or writes from the addressed register. Incrementing burst read and write is a sequence that begins with an address, and then reads or writes to/from each register in address order for as long as clocking continues. It is possible to repeatedly read (poll) a single register using a non-incrementing burst read. Absolute Maximum Ratings Storage Temperature .................................... -40C to +90C Ambient Temperature with Power Applied........ 0C to +70C Supply Voltage on any power supply pin relative to VSS-f0.3V to +3.9V DC Voltage to Logic Inputs[11].................. -0.3V to VIO +0.3V DC Voltage applied to Outputs in High-Z State...-0.3V to VIO +0.3V Static Discharge Voltage (Digital)[12].......................... >2000V Static Discharge Voltage (RF)[12]................................ 1100V Latch-up Current......................................+200 mA, -200 mA Ground Voltage.................................................................. 0V FOSC (Crystal Frequency)........................... 12 MHz 30 ppm DC Characteristics (T = 25C) Parameter VBAT VREG[13] VLVD VIO VCC Description Battery Voltage PMU Output Voltage Low Voltage Detect VIO Voltage VCC Voltage 0-70C 0-70C 2.7V mode LVDCR [2:0] set to 000 1.8 2.4 3.6 3.6 V V Conditions Min 1.8 2.7 2.73 Typ Max 3.6 Unit V V Device Current (For total current consumption in different modes, for example Radio, active, MCU, and sleep, add Radio Function Current and MCU Function Current) ICC (GFSK)[14] Average ICC, 1 Mbps, slow channel PA = 5, 2-way, 4 bytes/10 ms CPU speed = 6 MHz PA = 5, 2-way, 4 bytes/10 ms CPU speed = 6 MHz VCC = 3.0V, MCU sleep, PMU disabled VCC = 3.0V, MCU sleep, PMU enabled 9.87 10.2 2.72 30.4 mA mA A A ICC (32-8DR)[14] Average ICC, 250 kbps, fast channel ISB1 ISB2 Sleep Mode ICC Sleep Mode ICC Notes 11. It is permissible to connect voltages above VIO to inputs through a series resistor limiting input current to 1 mA. AC timing not guaranteed. 12. Human Body Model (HBM). 13. VREG depends on battery input voltage. 14. Includes current drawn while starting crystal, starting synthesizer, transmitting packet (including SOP and CRC16), changing to receive mode, and receiving ACK handshake. Device is in sleep except during this transaction. Document #: 001-07611 Rev *C Page 56 of 65 [+] Feedback CYRF69103 DC Characteristics (T = 25C) (continued) Parameter IDLE ICC Isynth TX ICC TX ICC TX ICC RX ICC RX ICC Boost Eff ILOAD_EXT Description Radio off, XTAL Active ICC during Synth Start ICC during Transmit ICC during Transmit ICC during Transmit ICC during Receive ICC during Receive PMU Boost Converter Efficiency Average PMU External Load current PA = 5 (-5 dBm) PA = 6 (0 dBm) PA = 7 (+4 dBm) LNA off, ATT on. LNA on, ATT off. VBAT = 2.5V, VREG = 2.73V, ILOAD = 20 mA VBAT = 1.8V, VREG = 2.73V, RX Mode CPU speed = 6 MHz CPU speed = 3 MHz At IOH = -100.0 A At IOH = -2.0 mA At IOL = 2.0 mA 0.76VIO 0 0 < VIN < VIO except XTAL, RFN, RFP, RFBIAS 4 Low to High edge High to Low edge High to low edge 40% 30% 3% 1.6 IOL1 = 50 mA IOL1 = 25 mA IOL2 = 8 mA IOH = 2 mA VCC - 0.5 1.4 0.4 0.8 [15] Conditions XOUT disabled Min Typ 1.1 8.6 21.2 28.5 39.9 18.9 21.9 83 Max Unit mA mA mA mA mA mA mA % Radio Function Currents (VCC = 3.0V, MCU Sleep) 15 mA MCU Function Currents (VDD = 3.0V) IDD1 IDD1 VOH1 VOH2 VOL VIH VIL IIL CIN RUP VICR VICF VHC VILTTL VIHTTL VOL1 VOL2 VOL3 VOH VDD Operating Supply Current VDD Operating Supply Current Output High Voltage Condition 1 Output High Voltage Condition 2 Output Low Voltage Input High Voltage Input Low Voltage Input Leakage Current Pin Input Capacitance Pull-up Resistance Input Threshold Voltage Low, CMOS mode Input Threshold Voltage Low, CMOS mode Input Hysteresis Voltage, CMOS Mode Input Low Voltage, TTL Mode Input HIGH Voltage, TTL Mode Output Low Voltage, High Drive[15] Output Low Voltage, High Drive Output Low Voltage, Low Drive Output High Voltage[16] 5.0 4.4 VIO - 0.1 VIO - 0.4 VIO VIO 0 0.4 VIO 0.24VIO 0.26 3.5 +1 10 12 65% 55% 10% 0.72 mA mA V V V V V A pF K VCC VCC VCC V V V V V V Radio Function GPIO Interface -1 MCU Function GPIO Interface Notes 15. Available only on P1.3,P1.4,P1.5,P1.6,P1.7. 16. Except for pins P1.0, P1,1 in GPIO mode. Document #: 001-07611 Rev *C Page 57 of 65 [+] Feedback CYRF69103 AC Characteristics Parameter GPIO Timing TR_GPIO TF_GPIO FIMO FILO SPI Timing TSMCK TSSCK TSCKH TSCKL TMDO TMDO1 TMSU TMHD TSSU TSHD TSDO TSDO1 TSSS TSSH SPI Master Clock Rate SPI Slave Clock Rate SPI Clock High Time SPI Clock Low Time Master Data Output Time[17] Master Data Output Time, First bit with CPHA = 0 Master Input Data Setup time Master Input Data Hold time Slave Input Data Setup Time Slave Input Data Hold Time Slave Data Output Time Slave Data Output Time, First bit with CPHA = 0 Slave Select Setup Time Slave Select Hold Time SCK to data valid Time after SS LOW to data valid Before first SCK edge After last SCK edge 150 150 High for CPOL = 0, Low for CPOL = 1 Low for CPOL = 0, High for CPOL = 1 SCK to data valid Time before leading SCK edge 125 125 -25 100 50 50 50 50 100 100 50 FCPUCLK/6 2 2.2 MHz MHz ns ns ns ns ns ns ns ns ns ns ns ns Output Rise Time Output Fall Time Internal Main Oscillator Frequency Internal Low-Power Oscillator Measured between 10 and 90% Vdd/Vreg with 50 pF load Measured between 10 and 90% Vdd/Vreg with 50 pF load With proper trim values loaded[5] With proper trim values loaded[5] 18.72 15.0001 50 15 26.4 50.0 ns ns MHz KHz Description Conditions Min Typ Max Unit Figure 19. Clock Timing TCYC TCH CLOCK TCL Note 17. In Master mode first bit is available 0.5 SPICLK cycle before Master clock edge available on the SCLK pin. Document #: 001-07611 Rev *C Page 58 of 65 [+] Feedback CYRF69103 Figure 20. GPIO Timing Diagram 90% GPIO Pin Output Voltage 10% TR_GPIO TF_GPIO Figure 21. SPI Master Timing, CPHA = 1 SS (SS is under firmware control in SPI Master mode) TSCKL SCK (CPOL=0) TSCKH SCK (CPOL=1) TMDO MOSI MSB LSB MISO MSB LSB TMSU TMHD Document #: 001-07611 Rev *C Page 59 of 65 [+] Feedback CYRF69103 Figure 22. SPI Slave Timing, CPHA = 1 SS TSSS TSCKL TSSH TSCKH SCK (CPOL=0) SCK (CPOL=1) MOSI TSDO MSB LSB TSSU TSHD MSB LSB MISO Figure 23. SPI Master Timing, CPHA = 0 SS (SS is under firmware control in SPI Master mode) TSCKL SCK (CPOL=0) TSCKH SCK (CPOL=1) TMDO1 TMDO MSB LSB MOSI MISO MSB LSB TMSU TMHD Document #: 001-07611 Rev *C Page 60 of 65 [+] Feedback CYRF69103 Figure 24. SPI Slave Timing, CPHA = 0 SS TSSS TSCKL TSSH TSCKH SCK (CPOL=0) SCK (CPOL=1) MOSI MSB LSB TSSU TSHD TSDO1 TSDO MSB LSB MISO Document #: 001-07611 Rev *C Page 61 of 65 [+] Feedback CYRF69103 RF Characteristics Table 76. Radio Parameters Parameter Description Conditions Min 2.400 -97 -93 -80 -87 -84 22.8 -31.7 LNA On LNA On -15 -6 21 1.9 C = -60 dBm, C = -60 dBm C = -60 dBm C = -67 dBm C = -67 dBm C = -64 dBm, f = 5,10 MHz 100 kHz ResBW 100 kHz ResBW 100 kHz ResBW PA = 7 PA = 6 PA = 5 PA = 0 seven steps, monotonic PN Code Pattern 10101010 PN Code Pattern 11110000 >0 dBm -6 dBc, 100 kHz ResBW 500 +2 -2 -7 9 3 -30 -38 -30 -36 -79 -71 -65 4 0 -5 -35 39 5.6 270 323 10 876 +6 +2 -3 Typ Max 2.497 Unit GHz dBm dBm dBm dBm dB dB dBm Count dB/Count dB dB dB dB dBm dBm dBm dBm dBm dBm dBm dBm dBm dB dB kHz kHz %rms kHz RF Frequency Range Subject to regulation Receiver (T = 25C, VCC = 3.0V, fOSC = 12.000 MHz, BER < 10-3) Sensitivity 125 kbps 64-8DR BER 1E-3 Sensitivity 250 kbps 32-8DR Sensitivity Sensitivity GFSK LNA Gain ATT Gain Maximum Received Signal RSSI Value for PWRin -60 dBm RSSI Slope Interference Performance (CER 1E-3) Co-channel Interference rejection Carrier-to-Interference (C/I) Adjacent (1 MHz) Channel Selectivity C/I 1 MHz Adjacent (2 MHz) Channel Selectivity C/I 2 MHz Adjacent (> 3 MHz) Channel Selectivity C/I > 3 MHz Out-of-Band Blocking 30 MHz-12.75 MHz[18] Intermodulation Receive Spurious Emission 800 MHz 1.6 GHz 3.2 GHz Transmitter (T = 25C, VCC = 3.0V, fOSC = 12.000 MHz) Maximum RF Transmit Power Maximum RF Transmit Power Maximum RF Transmit Power Maximum RF Transmit Power RF Power Control Range RF Power Range Control Step Size Frequency Deviation Min Frequency Deviation Max Error Vector Magnitude (FSK error) Occupied Bandwidth BER 1E-3 CER 1E-3 BER 1E-3, ALL SLOW = 1 Notes 18. Exceptions F/3 & 5C/3. 19. When using an external switching regulator to power the radio, care must be taken to keep the switching frequency well away from the IF frequency of 1MHz. Document #: 001-07611 Rev *C Page 62 of 65 [+] Feedback CYRF69103 Table 76. Radio Parameters (continued) Parameter Description Transmit Spurious Emission (PA = 7) In-band Spurious Second Channel Power (2 MHz) In-band Spurious Third Channel Power (>3 MHz) Non-Harmonically Related Spurs (8.000 GHz) Non-Harmonically Related Spurs (1.6 GHz) Non-Harmonically Related Spurs (3.2 GHz) Harmonic Spurs (Second Harmonic) Harmonic Spurs (Third Harmonic) Fourth and Greater Harmonics Power Management (Crystal PN# eCERA GF-1200008) Crystal Start to 10ppm Crystal Start to IRQ Synth Settle Synth Settle Synth Settle Link Turnaround Time Link Turnaround Time Link Turnaround Time Link Turnaround Time Max. packet length XSIRQ EN = 1 Slow channels Medium channels Fast channels GFSK 250 kbps 125 kbps <125 kbps < 60 ppm crystal-to-crystal all modes except 64-DDR and 64-SDR < 60 ppm crystal-to-crystal 64-DDR and 64-SDR 0.7 0.6 270 180 100 30 62 94 31 40 1.3 ms ms s s s s s s s bytes -38 -44 -38 -34 -47 -43 -48 -59 dBm dBm dBm dBm dBm dBm dBm dBm Conditions Min Typ Max Unit Max. packet length 16 bytes Document #: 001-07611 Rev *C Page 63 of 65 [+] Feedback CYRF69103 Table 77. Ordering Information Package 40-pin Pb-Free QFN 6x6 mm Ordering Part Number CYRF69103-40LFXC Package Diagram Figure 25. 40-pin Pb-Free QFN 6x6 mm TOP VIEW SIDE VIEW BOTTOM VIEW C 0.05[0.002] MAX. 0.80[0.031] MAX. 0.20[0.008] REF. 0.08[0.003] A 5.90[0.232] 6.10[0.240] 5.70[0.224] 5.80[0.228] N 1 0.60[0.024] DIA. 2 1.00[0.039] MAX. 18.5 0.18[0.007] 0.28[0.011] N PIN1 ID 0.20[0.008] R. 1 2 0.45[0.018] 5.70[0.224] 5.80[0.228] 5.90[0.232] 6.10[0.240] 18.5 0-12 0.30[0.012] 0.50[0.020] C SEATING PLANE 4.45[0.175] 4.55[0.179] 0.50[0.020] 0.24[0.009] 0.60[0.024] (4X) NOTES: 1. HATCH IS SOLDERABLE EXPOSED AREA 51-85190-*A 2. REFERENCE JEDEC#: MO-220 3. PACKAGE WEIGHT: 0.086g 4. ALL DIMENSIONS ARE IN MM [MIN/MAX] Document #: 001-07611 Rev *C Page 64 of 65 4.45[0.175] 4.55[0.179] SOLDERABLE EXPOSED PAD [+] Feedback CYRF69103 Document History Page Document Title: CYRF69103 Programmable Radio on Chip Low Power Document #: 001-07611 REV. ECN No. ** *A *B 479801 501282 631696 Orig. of Change OYR OYR BOO New advance data sheet. Preliminary data sheet. Created Preliminary data sheet from Advance Information. Final data sheet. Updated DC Characteristics table with characterization data. Minor text changes GPIO capacitance and timing diagram included Sleep and Wakeup sequence documented PIT Timer registers' R/W capability corrected to read only Updated radio function register descriptions Changed L/D pin description Changed RST Capacitor from 0.1uF to 0.47uF Added example PMU configuration circuits Updated to new template Description of Change *C 2447906 AESA (c) Cypress Semiconductor Corporation, 2006-2008. The information contained herein is subject to change without notice. Cypress Semiconductor Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a Cypress product. Nor does it convey or imply any license under patent or other rights. Cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement with Cypress. Furthermore, Cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges. Any Source Code (software and/or firmware) is owned by Cypress Semiconductor Corporation (Cypress) and is protected by and subject to worldwide patent protection (United States and foreign), United States copyright laws and international treaty provisions. Cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of, and compile the Cypress Source Code and derivative works for the sole purpose of creating custom software and or firmware in support of licensee product to be used only in conjunction with a Cypress integrated circuit as specified in the applicable agreement. Any reproduction, modification, translation, compilation, or representation of this Source Code except as specified above is prohibited without the express written permission of Cypress. Disclaimer: CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Cypress reserves the right to make changes without further notice to the materials described herein. Cypress does not assume any liability arising out of the application or use of any product or circuit described herein. Cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress' product in a life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges. Use may be limited by and subject to the applicable Cypress software license agreement. Document #: 001-07611 Rev *C Revised April 25, 2008 Page 65 of 65 PSoC is a registered trademark and WirelessUSB and PRoC are trademarks of Cypress Semiconductor Corporation. All products and company names mentioned in this document may be the trademarks of their respective holders. [+] Feedback |
Price & Availability of CYRF6910308
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |